Omnichannel Integration: How to manage the numbering of orders in multiple origins or business units

When you operate with multiple origins or business units, order numbering can become a challenge, especially if there is a chance that it will be repeated across these sources. Properly managing this situation is crucial to ensure a smooth experience for your customers and effective transaction tracking. In this article, we will explore two effective approaches to de-duplicating the order number in complex situations.

Use a different "StoreCode" for each transaction depending on the origin:

Using a different "StoreCode" for each transaction based on its origin is an effective way to avoid duplicate order numbers. By assigning a unique identifier for each source or business unit, it is possible to ensure that order numbers remain distinct and consistent across the platform.

For example, if you have two different origins, such as UN1 and UN2, and both start their numbering from 1, you could implement the following:

Transaction on UN1: StoreCode = UN1, Order Number = 1 (UN1-1)
Transaction on UN2: StoreCode = UN2, Order Number = 1 (UN2-1)

This strategy provides a clear and organized way to identify the source of each order and avoids potential numbering conflicts.

Append a PREFIX to the order number with reference to the origin or business unit:

Another viable option is to add a prefix to the order number, indicating the origin or the business unit to which it belongs. This practice helps to quickly distinguish the origin of the order and to maintain the unique numbering for each source.

Following the previous example, where we have UN1 and UN2 as origins, the implementation of this method would be the following:

Transaction on UN1: Order number = 1 (UN1-1)
Transaction on UN2: Order Number = 1 (UN2-1)

By adopting this strategy, order numbers would remain unique and make it easier to identify the associated business unit.

Consult our article: Omnichannel Integration Guide

Updated on: 08/15/2023