Packing point carriers

See which carrier is used at each packing point with which delivery type and cost by region.

Packing point carriers (OMS › Packing locations › Packing point carriers) lists the carrier cost by region for orders shipped from the packing point: which carrier is used at each packing point with which delivery type and cost.

This table is populated from the values in the Order fulfilment costs screen. We recommend making changes there: a row manually edited here will be overwritten with the profile value on the next Apply. If the value source is readable, a bar appears above the table indicating this and a Go to order fulfilment costs button appears; the button opens the Carrier cost tab of that screen.

Table

• Columns: Sales channel, Packing point (source of the point, with its storage below), Carrier, Delivery (To address, From store, To address and from store), Region 1–4, Fail-over, and Value source. You can sort by clicking the column header.
• Region columns are used according to the distance to the delivery province (see Distance groups screen). If 0 is entered for a region, it is calculated as 0; if left empty, the Fail-over cost is used and "Fail-over" is shown faintly in the table.
• From store rows are not changed by Order fulfilment costs; this is indicated in the Value source column.
• The To address and from store row of a managed carrier is split into two rows on the next Apply: the to address row with the profile price, and the from store row with the current price. The Value source column shows "Split into to address and from store on Apply"; this is not a deviation. If the carrier already has two rows, this row is removed.
• The expected value of the to address row includes the packing consumption cost from Order fulfilment costs; the deviation window shows this separately.
• Filters: Sales channel, Carrier, Code search (searches in packing source code and name, packing storage and carrier code, carrier name), and Only manually changed (if value source is readable). There is no separate search box in the column header.

Value source and manually changed rows

The Value source badge shows from which layer the value comes: General, group name, Source-specific, or Storage-specific; rows not managed by the profile show Undefined. Only rows of sales channels and carriers within the scope of Order fulfilment costs are managed by the profile; by default, carriers are all carriers the company works with. Rows of a carrier removed from the selection are not deleted, only not managed by the profile.

A row whose value differs from the profile has the badge Changed by hand; the changed cell is highlighted yellow and a strip appears below the row showing the profile value and what will be written on the next Apply. Clicking the strip's Keep or revert or the badge opens the Row differs from profile window:

• Keep as a storage-specific value: the table values are written to the profile for this storage; on the next Apply, other rows in this storage's scope also take these values; the window shows how many rows will change. A region left to Fail-over appears as "Fail-over (40)" in the window and that amount is saved. This option is disabled if the table value is negative.
• Revert to the profile value (or "… revert to value" if single field): only this row is written to OMS with profile values; previous values are kept in OMS audit logs. If the profile leaves a region to Fail-over, the expected value appears as "Fail-over".

Rows that will be deleted or replaced by another delivery type row on the next Apply are also indicated in this window.

Adding, editing, deleting

• New cargo mapping adds a new carrier row: enter Sales channel, Pack source, Pack storage, Carrier, Delivery, and region / Fail-over costs. Delivery defaults to To address.
  • The Carrier list shows only carriers the company works with. If this info is unreadable or no records exist, all carriers are listed.
  • A From store row can be added if an To address row for the same carrier and packing point exists (or vice versa). Rows with overlapping delivery locations (e.g. adding To address when To address and from store exists) are not added; the window indicates which row conflicts.
  • If the row was added by someone else in the meantime, nothing is written and the list refreshes; if the same values already exist, this is indicated.
• Edit costs changes the region and Fail-over costs of the row.
• Delete deletes only the selected delivery row; other delivery rows of the same carrier remain (e.g. deleting To address leaves From store). The delete window shows the row to be deleted and remaining delivery rows by name. If the row is managed by the Order fulfilment costs profile, this is also indicated: it may be rewritten on the next Apply. If the row was already deleted in the meantime, it says "already deleted"; if OMS does not respond in time, you are asked to check the row.
• Generate from TMS: generates bulk mappings from TMS carrier agreements for the selected sales channel. It does not affect existing records, adds missing ones with Initial cost as To address and from store. If the carrier is managed by Order fulfilment costs, these rows are split into To address and From store on the next Apply.

Cost boxes comply with entry rules in the Order fulfilment costs screen: up to 4 decimals, 0 or greater; ambiguous formats like "1.500" are rejected. Fail-over cannot be left empty (enter 0 for zero). Leaving a region box empty uses Fail-over for that region ("Empty: the fallback is used"); new rows start with empty region boxes.

Who sees what, who does what

• If you are not an inventory manager, New cargo mapping, Generate from TMS, and the Actions column are not visible.
• OwnerAdmin and TenantAdmin see and edit all packing points (distribution centers, HUBs, including vendors). Other users do not see rows of these points and cannot change their costs.
• Only OwnerAdmin and TenantAdmin can run Generate from TMS because it writes rows for all packing points of the sales channel; for others, the button is disabled with an explanation.
• If an action is disabled, the button appears faint and the reason is in the button tooltip. If the admin role is missing, a message "This action requires the OwnerAdmin or TenantAdmin role." appears once at the top of the screen.
• In permission preview (viewing as another user), adding, cost editing, generating from TMS, deleting, and the two window actions are disabled. If permission preview starts while a window is open, pressing Save or Delete closes the window and reports the reason.

Notes

• A row manually changed here is overwritten with the profile value on the next Apply unless "Keep as a storage-specific value" is selected.
• OMS location read permission is required to see value source; also source groups, value profile, and default packing point must be readable. If not, the badge and column are not shown and a warning appears. Values in the table are still those in OMS.
• Missing rows return with Preview and apply in the Order fulfilment costs screen.
• Deleting from MainUI deletes all delivery rows of the same carrier; adding from MainUI rejects a second delivery row for the same carrier and packing point if one already exists.
• Rows with missing keys (undefined carrier or delivery location) cannot be deleted here; only from MainUI, which deletes all delivery rows of the same carrier.
• Every change on this screen is backed up on the CommerceLab side.