Unleashed order settings

Every setting on the Unleashed Order Configuration, for sending sales orders into Unleashed and importing them back out, grouped by area with values, defaults and when to change each one.

These settings live on the Unleashed Order Configuration. Most of them control sales orders that Supply Lens sends into Unleashed. The settings under receive (at the end of this page) control orders Supply Lens imports out of Unleashed.

A setting left empty or unset simply switches its behaviour off, unless a default is shown. Many settings are tag maps: rules that apply a value to orders carrying a matching tag, with an optional default. How tag rules work explains them.

Order status

Unleashed has exactly five fixed statuses: Parked, Placed, Backordered, Completed and Deleted. Your account's own custom statuses (up to ten, such as Picking) go in a separate field.

Setting	What it does	Values / default	When to change it
Default order status `defaultOrderStatus`	The status a new sales order is created in.	One of the five fixed statuses. Unset: orders with a Paid financial status are `Placed`, all others `Parked`.	Set it when you want one status regardless of payment. Never put a custom status here: Unleashed rejects it without saying which field was wrong.
Order status rules `orderStatusMap`	A prioritised list of rules that set the status from a tag, the source Integration, or both. First match wins.	List of rules (fields below). Takes priority over `defaultOrderStatus`.	When different channels or kinds of order should arrive in different statuses.
Custom status rules `customStatusTagMap`	Maps order tags to one of your account's custom statuses, written to Unleashed's separate `CustomOrderStatus` field.	Tag map with an optional default.	When you use your own statuses.
Validate order statuses `validateOrderStatuses`	Before sending, checks the order's status against the statuses your account actually has, and fails with a message naming the valid ones. Catches a custom status put in `defaultOrderStatus`, and reports a retired custom status as obsolete rather than unknown.	On or off. Default on.	Leave it on. It only rejects orders Unleashed would refuse anyway, and gives a clearer message. If the statuses can't be read, the check is skipped and the order is sent as normal.
Complete fulfilled orders `completeFulfilledOrders`	Marks fully fulfilled orders `Completed` in Unleashed.	On or off. Default on.	Turn off if orders should stay open after fulfilment.
Delete cancelled orders `deleteCancelledOrders`	Deletes orders in Unleashed when they're cancelled in the source system.	On or off. Default on.	Turn off if cancelled orders should be handled by hand.

Each orderStatusMap rule has these fields. A rule needs tag, integrationKey or both; if both are set, both must match.

Field	What it is
`tag`	A partial tag to match against the order's tags.
`integrationKey`	The source Integration to match, for example a Shopify store's key.
`orderStatus`	The Unleashed status to apply when the rule matches.

Order numbers and customer reference

Setting	What it does	Values / default	When to change it
Use source order number `useSourceOrderNumberAsSalesOrderNumber`	Uses the source system's order number (for example the Shopify order number) as the Unleashed sales order number.	On or off. Off or unset: Unleashed numbers the order.	Turn on when you want the same number in both systems.
Use source order number by tag `useSourceOrderNumberAsSalesOrderNumberTagMap`	Overrides the setting above per order. Each entry maps a tag pattern to true or false.	Tag map.	When some channels should keep their own numbers and others shouldn't.
Buyer order number as customer reference `useBuyerOrderNumberAsCustomerRef`	Uses the buyer's purchase order number as the customer reference.	On or off. Unset: the order number is used.	For B2B orders where the customer's PO number matters.
Customer reference formatting `customerReferenceStringManipulationsBySourceIntegration`	Transforms the customer reference (for example trims it, adds a prefix or applies a regex replacement) per source Integration. Each key is a source integration key; each value is a string manipulation configuration.	Dictionary by integration key.	When a channel's references need tidying before they reach Unleashed.

Sales order group

The Sales Order Group categorises orders in Unleashed. The settings are checked in this order: tag map, then store key map, then store key, then default.

Setting	What it does	Values / default	When to change it
Group from store key `setSalesOrderGroupToStoreKey`	Sets the Sales Order Group to the source integration key (for example the Shopify store identifier).	On or off.	To group orders by channel.
Store key to group `storeKeyToSalesOrderGroupMap`	Maps source integration keys to your own group labels instead of the raw key.	Dictionary. Only works when `setSalesOrderGroupToStoreKey` is on.	When you want a friendly label per store.
Group from tag `setSalesOrderGroupFromTagValue`	Tag patterns checked against the order's tags. The first matching tag's value, or an explicit `data` value, becomes the group.	List of tag patterns.	When the group depends on the individual order.
Default group `defaultSalesOrderGroup`	The group used when no rule above gives one.	Text.	As a fallback.
Group by financial status `salesOrderGroupFinancialStatusMap`	Maps the order's financial status (for example `paid`, `pending`) to a group.	Map.	To separate orders by payment state.

Customers

Customer type, defaults and discount

Setting	What it does	Values / default	When to change it
Customer type by source `customerTypesBySourceIntegration`	A default Unleashed customer type per source integration key.	Dictionary with a default fallback.	When each channel's customers have their own type.
Customer type by tag `customerTypeTagMap`	Sets the customer type from a tag: the entry's `data` if given, otherwise the tag's own value.	Tag map. Takes priority over `customerTypesBySourceIntegration`.	When the type depends on the order.
Customer defaults `customerDefaultsTagMap`	A set of default values applied when creating or updating a customer (fields below).	Tag map. The `default` applies with no matching tag, so a blanket set needs no tags.	To give new customers a payment term, tax code, price tier and so on. Only configure the fields you need: the customer is written as a whole object, so a value here overwrites what Unleashed would otherwise default to.
Customer discount rate `customerDiscountRateTagMap`	Sets the discount rate on a created customer from a tag. No `data`: the tag's own value is used. With `data`: a fixed rate.	Tag map. A rate between 0 and 1 (a fifth off is `0.2`). Nothing configured or matched: no rate is written.	To carry a discount from a source such as B2B Wave. Point it at the rate tag, not the percentage one: nothing converts.

customerDefaultsTagMap entries can set these fields. paymentTerm and taxCode must already exist in your Unleashed account.

Field	What it is
`customerType`	Unleashed customer type.
`salesOrderGroup`	Default sales order group for the customer.
`deliveryMethod`	Default delivery method.
`defaultWarehouse`	Default warehouse code.
`sellPriceTier`	Sell price tier.
`paymentTerm`	Payment term, used only when the Document carries none of its own.
`taxable`	Whether the customer is taxable.
`taxCode`	Unleashed tax code name.

The documented customerDiscountRateTagMap for B2B Wave orders:

"customerDiscountRateTagMap": {
  "items": [
    { "source": "b2b-wave", "key": "customer_discount_rate" }
  ]
}

Good to know

The discount rate doesn't discount the order the tag came from. A source such as B2B Wave has already applied its discount to the lines. The rate governs orders raised inside Unleashed afterwards.

Finding and updating customers

Setting	What it does	Values / default	When to change it
Source identifier as customer code `allowCustomerSourceIdentifierForCustomerCode`	Lets the source system's customer identifier be used as the Unleashed customer code when looking up or creating customers.	On or off. Default on.	Leave on to match by code.
Find customers by email `searchForCustomersByEmail`	Finds the customer by a customer contact's email address instead of by code.	On or off.	For sources that know who the customer is but share no code. The order fails if the contact has no email, no customer has it, or more than one does. Matches are re-checked exactly, because Unleashed's own email filter is a prefix match.
Find by email by tag `searchForCustomersByEmailTagMap`	Turns email search on or off for orders with a matching tag.	Tag map. `searchForCustomersByEmail` applies when no tag matches.	When only some channels should match by email.
Don't update existing customers `skipCustomerUpdateIfExists`	Existing customers are never updated; only new ones are created.	On or off.	When customer data is managed in Unleashed.
Prefer person's name for customer name `prioritiseNameForCustomerName`	Prefers the individual's name over the company name for the customer name.	On or off.	Consumer channels where most orders have no company.
Don't send customer email `customerExcludeEmailAddress`	The customer's email address isn't sent to Unleashed.	On or off.	When emails shouldn't reach Unleashed.

Stop credit

Setting	What it does	Values / default	When to change it
Fail on stop credit `failIfCustomerOnStopCredit`	Fails the order if the matched customer has Stop Credit on in Unleashed.	On or off.	When no order should reach Unleashed for a customer on stop.
Run maps on stop credit `runMapsOnCustomerStopCredit`	Map IDs to run when the customer is on stop credit, instead of failing.	List of map IDs.	To route the order to a different workflow rather than fail it.

Salespeople

Setting	What it does	Values / default	When to change it
Salesperson by store `storeKeyToSalesPersonMap`	Maps source integration keys to a salesperson name.	Dictionary.	When each store has its own rep.
Salesperson by tag `salesPersonTagMap`	Sets the salesperson from a tag, with an optional default. Tag values support `*` wildcards and `^…$` regular expressions.	Tag map. Most specific source: beats `storeKeyToSalesPersonMap`, which beats any salesperson already on the Document.	When the rep depends on the individual order. The name must match an Unleashed salesperson's full name or email exactly, or it's dropped with a warning (the order isn't failed).
Salesperson email by tag `salesPersonEmailTagMap`	Sets the salesperson's email address from a tag, alongside the name. No `data`: the tag's value. With `data`: a fixed address. Omit `source` to accept the tag from any Integration.	Tag map. Nothing is read without a rule.	Recommended where available: matching prefers the email, which survives renames and spelling differences. Tags written today: `b2b-wave:sales_person_email` and, on a round trip, `unleashed:sales_person_email`.
Set salesperson on customer `setCustomerSalesPerson`	Also sets the order's resolved salesperson on the customer written with it. Only a salesperson resolved to an Unleashed id is written.	On or off. Default off.	For new wholesale accounts that should arrive with a rep. Pair it with `skipCustomerUpdateIfExists`, or the rep is re-stamped on every order and undoes changes made in Unleashed.
Load customer's salesperson `loadDefaultSalesPerson`	Loads the default salesperson on the Unleashed customer and applies it to the order.	On or off.	When reps are held on customers in Unleashed. With `setCustomerSalesPerson` also on, the first order decides the rep and later orders read it back.

The documented examples:

"salesPersonTagMap": {
  "items": [
    { "source": "faire", "key": "source", "value": "FAIRE_DIRECT", "data": "Mark Wallis" }
  ],
  "default": "Will Harrald"
}

"salesPersonEmailTagMap": {
  "items": [
    { "source": "b2b-wave", "key": "sales_person_email" }
  ]
}

Delivery names and addresses

Setting	What it does	Values / default	When to change it
Save address to customer `saveAddress`	Saves the order's delivery address back to the Unleashed customer, but only when a delivery name is present.	On or off.	When the customer record should keep the latest address.
Prefer person's name for delivery name `prioritiseNameForDeliveryName`	Prefers the individual (ship-to) name over the company name for the delivery name.	On or off.	Consumer deliveries.
Prefer person's name for address name `prioritiseNameForAddressName`	Prefers the individual's name over the company name for the address contact name.	On or off.	Consumer deliveries.
Customer address as postal address `useCustomerAddressAsPostalAddress`	Copies the customer's billing or account address into the order's Postal Address fields.	On or off.	When the postal address should be filled.
Ship-to as physical address `useShipToAddressAsPhysicalAddress`	Copies the order's ship-to address into the order's Physical Address fields.	On or off.	When the physical address should be filled.
Combine company and name `deliveryNameCombineCompanyNameAndName`	Combines the company name and individual's name into one delivery name.	On or off. Format defaults to `{company}, F.A.O. {name}`.	When couriers need both.
Combined name format `deliveryNameCombinationString`	A .NET format string for the combined name: `{0}` is the company, `{1}` the individual.	Text. Default `{0}, F.A.O. {1}`.	To change the combined format.
Shipment details in comments `storeShipmentInformationInComments`	Puts the ship-to name and company in the comments field; when the order is read back, they're extracted again.	On or off.	When you need those details to survive a round trip.
Location from delivery name `deliveryNameIdentifierRegex`	A regular expression that extracts a location identifier from the delivery name.	Regex. Unset: no extraction.	When store or branch codes are held in the delivery name.

Delivery contacts

These settings match the order's contact against the customer's contacts in Unleashed. See Delivery contacts and customer pre-create for a walk-through.

Setting	What it does	Values / default	When to change it
Set delivery contact `setDeliveryContact`	Matches the ship-to contact (falling back to the customer contact) against the customer's contacts, and references the match on the order.	On or off. Default off: no delivery contact is sent.	When the carrier needs the delivery contact. A contact matches only when first name, last name, email and telephone all match. Some orders fail on purpose (see below). When nothing matches, no contact is sent.
Create missing delivery contact `createDeliveryContactIfMissing`	Adds an unmatched contact to the customer in Unleashed, marked for shipping, and uses it.	On or off. Off: an unmatched contact means none is sent.	When contacts should be built up automatically. Only one is created per customer per run.
Create delivery contact address `createDeliveryContactAddress`	Gives a matched or created contact with no default delivery address the order's delivery address as one, adding it to the customer as a `Shipping` address first if needed.	On or off. Default off.	Alongside the settings above. A contact that already has a default is never changed.
Use contact's default address `deliveryContactUseDefaultDeliveryAddress`	Asks Unleashed to use the matched contact's default address for the order's Delivery Address.	On or off.	Only takes effect when that default is the order's own delivery address (same name, `Shipping` address at the same place). Otherwise the order keeps its own address. No effect unless a contact was matched.

How matching works in detail:

Name and email are compared ignoring case, and a blank matches only a blank.
Telephone formatting (spaces, dashes, brackets) is ignored, and the number may be the contact's phone, mobile or office number. 07700 900001 and +44 7700 900001 count as different numbers.
There's no looser fallback to the name alone.
The address created by createDeliveryContactAddress is named after the order's delivery name. If a different address already has that name, the next free name is used: Alex Jones (2), Alex Jones (3) and so on. Unleashed overwrites a Shipping address with the same name without an error, which is why namesakes get numbered names.
A Postal address is never made a contact's default.
If Unleashed refuses the address or contact update, a warning is logged and the order is sent with its own delivery address.

Some orders fail on purpose

Unleashed won't hold two contacts with the same first name, last name and email. If the customer already has a contact with the order's name and email (or name and no email) but a different telephone, the order can neither use that contact nor create a new one. It fails with a message naming both contacts and both numbers. Give the delivery contact a distinguishing email, or correct the telephone in Unleashed.

Good to know

Since August 2026 Unleashed ignores a delivery contact's name, email and phone on write, and reads a contact with no identifier as an instruction to clear the one on the order. That's why nothing is sent when no contact matches.

Delivery methods

Setting	What it does	Values / default	When to change it
Copy warehouse to delivery method `copyWarehouseCodeToDeliveryMethod`	Writes the order's warehouse code into the delivery method field too.	On or off.	When delivery method should show the warehouse.
Warehouse codes to copy `copyWarehouseCodeFilter`	Limits the copy to the warehouse codes listed.	List. Empty: all codes are copied. Only works with `copyWarehouseCodeToDeliveryMethod`.	To copy only some warehouses.
Local pickup delivery method `localPickupDeliveryMethodName`	The delivery method name used when a shipping line is identified as local pickup.	Text.	When you offer collection.
Delivery method from shipping line `shippingLineDeliveryMethodMap`	Maps shipping line attributes (such as carrier or shipping method name) to an Unleashed delivery method.	Map.	To translate channel shipping options.
Delivery method by tag `deliveryMethodTagMap`	Maps order tags to a delivery method.	Tag map with a default fallback.	When the method depends on the order.

Shipping lines

Setting	What it does	Values / default	When to change it
Shipping product code `shippingProductCode`	Creates shipping charges as a product line with this code, rather than as a charge.	Product code.	When shipping should be a product line in Unleashed.
Shipping product by line `shippingLineProductCodeMap`	Maps individual shipping lines (matched on properties such as carrier or title) to product codes.	Map with a default fallback.	When different shipping services need different products.
Shipping Xero sales account `shippingLineXeroSalesAccount`	Sets the sales account code on shipping lines sent to Xero via Unleashed's Xero integration.	Account code.	When shipping should post to its own Xero account.
Mixed-tax shipping `handleMixedTaxShippingLines`	Handles shipping lines with a mix of taxable and non-taxable amounts specially, so tax is calculated correctly.	On or off.	When shipping can be partly taxable.

Discounts and charges

Without a product code, an adjustment is created as a generic Charge line. Mapping it gives a proper, named line. Adjustments are matched on their code, reason, whether they're a charge or a discount, and a minimum or maximum amount. Code and reason matching is exact and case-sensitive.

Setting	What it does	Values / default	When to change it
Discount product codes `discountProductCodeMap`	Maps discount adjustments to Unleashed product codes, so they become product lines.	Map with a default fallback.	To give discounts their own products.
Charge product codes `chargeProductCodeMap`	Maps charge adjustments (surcharges, fees) to product codes.	Map with a default fallback.	To give charges their own products.
Adjustment descriptions `adjustmentDescriptionMap`	Sets the description on the created line, replacing the default `Charge: …` or `Discount: …` text.	Map.	For clearer line descriptions.
Adjustment Xero sales accounts `adjustmentXeroSalesAccountMap`	Sets the Xero sales account (GL code) on the created line.	Map.	When adjustments should post to particular Xero accounts.

The documented example gives Faire's brand discount and commission their own products:

"discountProductCodeMap": {
  "items": [
    { "adjustmentReason": "Brand Discounts", "isCharge": false, "value": "DISCOUNT" },
    { "adjustmentReason": "Commission",      "isCharge": false, "value": "COMMISSION" }
  ]
}

Good to know

A line created this way doesn't round-trip: if orders are also imported back from Unleashed, it's read as an ordinary product line, not an adjustment.

Tax

Setting	What it does	Values / default	When to change it
Taxes as separate lines `groupTaxesAsLineItems`	Breaks taxes out of the line prices and adds them as separate lines or charges.	On or off.	When the source's tax should appear as its own lines.
Countries excluded from tax lines `groupTaxesExcludedCountries`	Unleashed country IDs (GUIDs) excluded from `groupTaxesAsLineItems`; their taxes are handled normally.	List of country GUIDs.	When tax lines only suit some destinations.
Product codes for tax lines `productCodeForTaxLines`	Maps tax rates (as decimals, for example `0.15` for 15%) to product codes, so tax lines become product lines.	Dictionary. Used with `groupTaxesAsLineItems`.	When tax lines need specific products.
Order tax rate from lines `setOrderTaxRateFromLines`	Sets the order's overall tax rate to the largest rate found on its lines.	On or off.	When the order-level rate should follow the lines.
Match to nearest tax rate `matchToNearestTaxRate`	Matches the incoming tax rate to the nearest rate set up in Unleashed instead of requiring an exact match.	On or off.	When source rates don't match Unleashed's exactly.

Rounding

Unleashed can lose precision with tax-inclusive prices, or when large quantities need unit prices with more than four decimal places. These settings reconcile the totals. See Rounding in Unleashed.

Setting	What it does	Values / default	When to change it
Add rounding adjustments `tryCalculateRoundingAdjustments`	Tries to add a rounding adjustment line so the Unleashed total matches the source total.	On or off.	When totals drift by pennies.
Rounding tolerance `roundingTolerance`	The largest difference (in order currency) accepted as rounding. Bigger differences aren't silently adjusted.	Amount.	To set how much drift is acceptable.
Tax rate for rounding `taxRateForTaxRoundingAmounts`	The tax rate applied to rounding adjustments.	Rate. Unset: the largest rate on the order, or `1` (100%) as a last resort.	When rounding lines need a specific rate.
Line total decimals `lineTotalRoundingDecimals`	Decimal places used when rounding each line total, to stop rounding errors building up.	Number.	Orders with many lines.

Dates

Setting	What it does	Values / default	When to change it
Order date as required date `useOrderDateAsRequiredDate`	Uses the source order date as the Required Date too.	On or off.	When the source sends no required date.
Required date as order date `useRequiredDateAsOrderDate`	Uses the source Required Date as the Unleashed order date.	On or off.	When orders should be dated by when they're needed.
Adjust required date `adjustSalesOrderRequiredDate`	An offset added to the Required Date, as a `TimeSpan`.	For example `1.00:00:00` adds one day.	To allow for lead time.
Adjust dispatch date `adjustSalesShipmentDispatchDate`	An offset added to the dispatch date when creating a sales shipment, as a `TimeSpan`.	Duration.	To shift shipment dates.

Products, assemblies, serials and batches

Setting	What it does	Values / default	When to change it
Product code for missing SKUs `defaultProductCodeWhenMissingSku`	The placeholder product code used for order lines with no SKU.	Product code.	So lines without a SKU can still be created.
Auto-complete assemblies `autoCompleteAssemblies`	Completes assembly orders created from sales order lines.	On or off. Applies when orders are sent to Unleashed.	When assemblies need no manual step.
Assemble-by date from required date `setAssemblyAssembleByDatesToRequiredDate`	Sets the Assemble By date on generated assemblies to the order's Required Date.	On or off.	When assembly should be scheduled against delivery.
Complete parked assemblies on import `autoCompleteParkedAssemblies`	When importing orders from Unleashed, completes any `Parked` assembly attached to an order line before importing the order. Other statuses are untouched.	On or off. Default off.	When assemblies must be complete before an order flows on. If one can't be completed, the order isn't imported and is only retried when next modified in Unleashed, so act on the logged error.
Assign serials and batches `serialBatch`	Auto-assigns serial and batch numbers to lines when the order is created.	On or off.	When you track serials or batches.
Serials and batches by tag `serialBatchTagMap`	Overrides `serialBatch` per order by tag (true or false).	Tag map. `serialBatch` applies when no tag matches.	When only some orders should be auto-assigned.

Accounting and sales shipments

Setting	What it does	Values / default	When to change it
Journal only `sendAccountingJournalOnly`	Sends only an accounting journal to Xero or QuickBooks Online, not the invoice.	On or off.	To record the financial impact without a customer-facing invoice.
Journal only by source `sendAccountingJournalOnlyBySourceIntegration`	The same, per source Integration.	By integration key.	When only some stores should send journals.
Journal only by tag `sendAccountingJournalOnlyByTag`	The same, per order by tag.	Tag map.	When it depends on the order.
Create sales shipment `createSalesShipment`	Creates a sales shipment in Unleashed when the order is processed.	On or off.	When shipments should be raised automatically.
Leave non-stock items off shipments `stripNeverDiminishingProductsFromShipment`	Excludes "never diminishing" (non-inventory) products from the generated shipment.	On or off.	When service or non-stock lines shouldn't be shipped.

References, comments and weight

Setting	What it does	Values / default	When to change it
Reference matching `referenceMatches`	Rules that extract reference values (such as PO numbers or customer references) from fields on the incoming order (fields below).	List of rules.	When references are buried in other fields.
Tags in comments `includeTagsInComments`	Appends the order's source tags to the comments field.	On or off.	For visibility in Unleashed.
Weight unit `weightUnit`	The unit order line weights are recorded in. Must match your Unleashed account's setting, which the API doesn't expose.	`kg`, `g`, `lb` or `oz`. Empty or unrecognised (the default): line weight isn't imported.	When importing orders and weights matter.
Weight from alternate units `weightFromAlternateUnits`	When a line and its product have no weight, works one out from the alternate unit with the lowest conversion rate that has a weight.	On or off. Default off. No effect without `weightUnit`.	When only case weights are recorded. Runs slightly heavy, as case weights usually include packaging.

Each referenceMatches rule has these fields:

Field	What it is
`type`	The type of Document reference to fill.
`source`	Which field on the order to read from.
`regexPattern`	A regular expression to match against the value.
`regexReplacement`	An optional replacement applied to the match.
`groupName`	The named capture group to extract.
`groupIndex`	The numbered capture group to extract.
`requiredForImport`	If true, the order is rejected when the rule doesn't match.

How weight is worked out: Unleashed supplies the total weight for each line, which becomes the line weight, and the per-unit weight is that total divided by the ordered quantity. A line raised before its product was weighed has no weight, so it takes the product's weight (in the same unit) as its per-unit weight.

Importing orders from Unleashed (`receive`)

These settings control orders imported out of Unleashed. See Orders out of Unleashed.

Setting	What it does	Values / default	When to change it
Setup date `receive.setupDate`	Only orders dated on or after this date are imported.	Date.	Set it to your go-live date so history isn't imported.
Last modified `receive.lastModifiedOn`	The timestamp of the most recently imported order; only orders modified after it are fetched.	Managed automatically.	Don't normally change it.
Statuses to import `receive.orderStatuses`	The statuses eligible for import.	List. Default `["Placed"]`.	Add other statuses only if those orders should flow onwards.
Cancelled statuses `receive.cancelledStatuses`	Order or custom statuses meaning an already-imported order was cancelled. It isn't imported again: its Document is tagged `unleashed:status:` plus the status, and its fulfilment status set to `Cancelled`, which passes the cancellation on (Pipedrive, for example, marks the deal lost).	List. Default `[]`. Matched against the custom status first, then the order status, ignoring case.	So cancellations reach downstream systems. Include `"Deleted"` for deleted orders. Custom statuses only exist on `Parked` orders.
Customers to skip `receive.customerCodeExclusionList`	Skips orders for these customer codes.	List.	To keep internal or test accounts out.
Customers to include `receive.customerCodeInclusionList`	When not empty, imports only orders for these customer codes.	List (allowlist).	To import one set of customers.
Warehouses to skip `receive.warehouseCodeExclusionList`	Skips orders assigned to these warehouses.	List.	To leave some warehouses out.
Warehouses to include `receive.warehouseCodeInclusionList`	When not empty, imports only orders assigned to these warehouses.	List (allowlist).	When one warehouse is run by a 3PL.
Import serials and batches `receive.serialBatch`	Includes serial and batch numbers on imported lines.	On or off.	When the receiving system needs them.
Customer and ship-to from original `receive.getCustomerAndShipToFromOriginalTargetData`	Finds the original Document that created the order in Unleashed and uses its customer and ship-to details.	On or off.	When the Unleashed record may have been edited since.
Load full customer record `receive.loadDetailedCustomerInformation`	Loads the full customer record rather than the summary on the order.	On or off.	When the receiving system needs fields the order doesn't carry.

Deleted in receive.orderStatuses still raises a deleted order as before, and now tags it too.

Unleashed order settings

Order status

Order numbers and customer reference

Sales order group

Customers

Customer type, defaults and discount

Finding and updating customers

Stop credit

Salespeople

Delivery names and addresses

Delivery contacts

Delivery methods

Shipping lines

Discounts and charges

Tax

Rounding

Dates

Products, assemblies, serials and batches

Accounting and sales shipments

References, comments and weight

Importing orders from Unleashed (receive)

Importing orders from Unleashed (`receive`)