Cin 7 Core Special Fields
Last updated: August 25, 2026
Our Cin7 Core integration has a few special case fields in its configuration. This article outlines those fields and how they are used by the integration.
Field | Description | Workflow |
Sales Tax Rule | The sales tax rule for this product when it appears in POs | PO Sync |
Location | The warehouse from which this product will be shipped | Fulfillment Sync |
Sales Tax Rule
The sales tax rule is the sales tax rule to use for a given product's line item when syncing POs to Cin7 Core. This dictates how Cin7 Core handles sales tax.
Location
Location is the warehouse from which an item is fulfilled. This data can take two forms, the first is simple text. The second is a more complicated JSON object. When location is text, a given product will always be fulfilled from the same warehouse.
Fulfillment Rules
If you need the fulfillment rules functionality defined below please reach out to Crstl support.
Fulfillment rules are used when a product can be served from multiple locations. Fulfillment rules uses a ship to address on a given PO as a basis to choose which warehouse to fulfill from. An example fulfillment rule JSON is the following:
{
"_id": "68c1dbb3305e90fe30301bba",
"field": "ship_to_city",
"mappings": [
{
"org_location": "Location - 1",
"trading_partner_location": "Atlanta"
},
{
"org_location": "Location - 2",
"trading_partner_location": "San Francisco"
}
]
}In this case field specifies the "ship to city", ie the city field of the ship to address. If this matches the trading partner location in the "mappings" list we will use that org_location as the location when syncing to Cin7 Core.
This fulfillment rule will function in the following manner:
PO has Ship to City = "Atlanta" - the location used will be "Location - 1"
PO has Ship to City = "San Francisco" - the location used will be "Location - 2"
PO has a different ship to city - the fulfillment will fail to sync to Cin7 Core because of a lack of location.