Coda Commerce settings

Every setting on the Coda Commerce Order and Shipment Configurations, from shipping service maps to the rolling shipment import window.

The Coda Commerce connector has two Configurations: Coda Commerce Order, whose settings translate shipping services, and Coda Commerce Shipment, whose settings control when shipments are imported.

Shipping services (orders)

These settings are on the Coda Commerce Order Configuration.

Setting	What it does	Values / default	When to change it
Shipping service name map `shippingServiceNameMap`	Maps Coda Commerce shipping service names to the values the downstream system expects, such as your internal shipping codes or names.	A map. A default can be set for services with no explicit mapping.	Set it when the target uses different names for shipping services. Set a default so a new service doesn't arrive blank.
Shipping service carrier code map `shippingServiceCarrierCodeMap`	Maps Coda Commerce shipping service names to carrier codes, deciding which carrier code goes on the order.	A map. A default can be set for services with no explicit mapping.	Set it when the target needs a carrier code. Build it from the same list of services as the name map.

Good to know

The guide doesn't show the JSON shape of these maps. Start from Create Default JSON and follow the shape it gives you.

Shipment import

These settings are on the Coda Commerce Shipment Configuration.

Setting	What it does	Values / default	When to change it
Import delay `importDelay`	Waits before importing a shipment, so other systems can update it first.	A duration, for example `00:05:00` for five minutes.	Set it when another system changes shipments after they're created.
Import time span `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.	A duration.	Make it comfortably longer than the longest time the Integration might be paused.

A rolling window

importTimeSpan counts back from now. A shipment older than the span is never imported, so if the Integration is paused for longer than the span, shipments created during the pause are missed.