Set up Coda Commerce
Lesson 25 of 30 5 min read
Translate shipping service names into the names and carrier codes the target expects, and import shipments within a rolling time window.
Coda Commerce has a connection form in Supply Lens and two Configurations: Order and Shipment. Its order settings are all about shipping services, translating Coda Commerce's names into what the other system expects. Its shipment settings control timing.
By the end of this lesson you'll be able to configure both and explain how importTimeSpan
differs from the usual import window.
Orders: shipping service maps
| shippingServiceNameMap | Maps Coda Commerce shipping service names to the values the downstream system expects, such as your internal shipping codes or names. A default can be set for unmapped services. |
|---|---|
| shippingServiceCarrierCodeMap | Maps Coda Commerce shipping service names to carrier codes, deciding which carrier code goes on the order. A default can be set for unmapped services. |
Build both from the same list of services: one gives the service its target name, the other its carrier. Set defaults on both so a new service doesn't arrive blank.
Shipments: a rolling window
| importDelay | Wait before importing a shipment so other systems can update it first. |
|---|---|
| importTimeSpan | Only shipments created within this span of now are imported. 24:00:00 means the last 24 hours only, even if older shipments are otherwise eligible. |
importTimeSpan is a moving window, not a fixed start date. It stops old shipments flooding in,
but it also means a shipment older than the span is never picked up. If the Integration is
paused for longer than the span, shipments created during the pause are missed.
Size the window to your outages
Make importTimeSpan comfortably longer than the longest time the Integration might be paused
or the schedule might miss, for example several days rather than 24 hours.
Good to know
The guide doesn't say which way Coda Commerce orders travel. Check the Send and Receive options on the Order Configuration for the customer's flow.
Brightwater Drinks and a weekend outage
Brightwater Drinks set importTimeSpan to 24:00:00. The Integration was disabled over a long
weekend for a system upgrade and shipments created on Saturday were never imported. The
implementer widens the span to several days and reruns the import; the missed shipments arrive.
shippingServiceCarrierCodeMap gets a default after a new "Pallet" service arrived with no
carrier code.
Recap
- Coda Commerce order settings map shipping service names to target names and carrier codes; set defaults on both.
importTimeSpanis a rolling window back from now.- Shipments older than the window are never imported, so size it beyond likely outages.
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.