How should sales orders be created in Enterpryze?
Lesson 8 of 15 8 min read
The Order settings that decide how a sales order looks in Enterpryze, from document type and shipping lines to sales person, due date and address format.
You have chosen a Business Partner strategy and aligned your SKUs. Now you can shape the sales orders themselves. This lesson works through the Order Configuration's settings for creating documents in Enterpryze, grouped by the question each one answers. The settings for new Business Partners were covered in the previous module, and the settings for picking documents up from Enterpryze come in a later lesson.
To change a setting, open the Integration tile, click Configurations, open the Order Configuration and edit its JSON.
What kind of document, and who hears about it?
| docType | The Enterpryze document type used when creating documents from orders. It decides how the order is classified within Enterpryze. |
|---|---|
| sendEmail | When true, Enterpryze sends an email notification when the document is created, to alert the relevant people. |
Guidance: keep the docType from the default JSON unless your Enterpryze administrator tells you orders should be created as a different document type. Turn sendEmail on only if someone in your team actually acts on the notification. At high volume, an email per order quickly becomes noise.
Which lines are shipping, not products?
| shippingLineItemCodes | A list of line item codes that represent shipping charges. Lines with these codes are treated as shipping costs rather than product lines. |
|---|
Guidance: if your storefront sends shipping as a line with a code (for example SHIPPING or DELIVERY), list every such code here. A code that is not listed is handled as an ordinary product line, which is rarely what you want for a delivery charge.
Who is the sales person?
| salesPersonIdMap | Sets the Enterpryze sales person. Each key is a sales person name as it appears on the order (matched ignoring case and surrounding spaces). Each value is the 24-character Enterpryze sales person id, such as 69970ff2d669a16c56df7593. Falls back to default when the order has no sales person or no key matches. |
|---|
Guidance, choose one of three patterns:
- Everyone the same: set only
default, and every order gets that sales person. Useful for a web channel owned by one person. - By name: list each name that appears on your orders, plus a
defaultfor the rest. - Leave it to Enterpryze: leave the map empty. With nothing matched and no
default, the field is left off and Enterpryze applies its own default.
"salesPersonIdMap": {
"Priya Shah": "69970ff2d669a16c56df7593",
"default": "69970ff2d669a16c56df7a01"
}
When is it due?
| defaultDueDateDays | The number of days after the order date to use as the default due date. When set, it gives the order an expected payment or delivery date. |
|---|
Guidance: set this if your team plans or chases against the due date in Enterpryze. For example, 3 if you promise despatch within three days.
How should the ship-to address read?
| includeNameInShipToFullAddress | When true, the contact name is included in the full ship-to address. When false, the address is formatted without the recipient name. |
|---|---|
| useFixedFormatForShipToFullAddress | When true, the ship-to address uses a fixed template instead of the dynamic format, so every order is formatted consistently. |
Guidance: include the name when the ship-to address is printed on despatch paperwork and the courier needs a recipient. Use the fixed format if addresses from your storefront arrive in inconsistent shapes and your team wants them to look the same every time.
Do you need extra fields filled in?
| customFieldMapping | Maps Enterpryze custom field names to values taken from the source document, so custom fields in Enterpryze are filled from the system the order came from. |
|---|
Guidance: use this when your Enterpryze has custom fields your team relies on, such as the storefront order number or a sales channel. The field must already exist in Enterpryze: a custom field id that does not exist is rejected.
Fernhill's Order settings
Fernhill's WooCommerce orders carry a shipping line with the code SHIPPING, so Fernhill adds it to shippingLineItemCodes. All web orders belong to the e-commerce manager, so salesPersonIdMap has only a default. Fernhill sets defaultDueDateDays to 2, includes the name in the ship-to address because the warehouse prints it on labels, and leaves sendEmail off: 60 emails a day would be ignored.
Recap
docTypeclassifies the order in Enterpryze.sendEmailnotifies people when it is created.- List every shipping code in
shippingLineItemCodes, or shipping lines are treated as products. salesPersonIdMapsets the sales person by name, with adefault, or leaves it to Enterpryze.defaultDueDateDaysand the two ship-to address settings shape the order your team works from.customFieldMappingfills custom fields, which must already exist in Enterpryze.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.