Manhattan settings and gotchas
Lesson 16 of 28 5 min read
Configure Manhattan carrier, service and order type translation, and the import window and references for shipments.
The Manhattan settings fall into three decisions: how carriers and services are translated, how the order type is chosen, and how shipments come back.
Decision 1: carriers and services
| carrierMap | Maps carrier names from the source system to Manhattan carrier values. Evaluated in order, with a default when nothing matches. |
|---|---|
| carrierServiceMap | Maps carrier service names to Manhattan carrier service codes. Supports a default. |
Carrier and service are separate in Manhattan, so you usually need both maps. A source order
that says "DPD Next Day" might map to carrier DPD and service NEXTDAY in Manhattan's
terms. Agree the exact values with the warehouse.
Pick defaults deliberately
A default means unmapped carriers still reach Manhattan with some value. That keeps orders flowing, but can hide a new carrier nobody mapped. Decide which the customer prefers.
Decision 2: order type
| tagToOrderTypeMap | Maps order tags to a Manhattan order type. The first matching tag decides; a default applies when no tags match. |
|---|
Warehouses often handle order types differently: retail store replenishment, wholesale and direct-to-consumer may be picked and packed in different ways. If the source system tags orders by channel, this map turns those tags into Manhattan order types.
Decision 3: shipments back
| setupDate, lastImportDate, importDelay | The standard import window. setupDate stops historical shipments being imported at go-live; lastImportDate is managed by the system. |
|---|---|
| orderIdReferenceType | The reference type for the Manhattan order id, used to link shipments to their original orders. |
| erpOrderReferenceType | The reference type preserving the ERP order id on imported shipments. |
Gotchas checklist
- Both carrier and service maps filled in, with agreed Manhattan values.
- A decision on defaults: keep orders flowing, or surface unmapped carriers.
- Order types mapped from tags that the source system really sets.
- The same reference types on the Order and Shipment groups.
Harbour Home adds a carrier
Harbour Home starts using a new courier for bulky items. Orders flow, but the warehouse
reports they all arrived with the default carrier. The implementer adds the new courier to
carrierMap and its services to carrierServiceMap, and the next orders carry the right
values.
Recap
- carrierMap and carrierServiceMap translate carriers and services separately, each with a default.
- tagToOrderTypeMap chooses the Manhattan order type from the first matching tag.
- Shipments use the standard import window plus the two reference types.
- When a new carrier appears, update both maps.
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.