By default, ROM calculates ATPClosed The quantity of inventory that can be used to fulfill orders on or before a specific date. Also called Available to Promise. inventory across the Inventory Organization and returns the result in the Quantity Request API. However, ROM also enables you to calculate ATP inventory by SellerClosed A seller is part of an organization. It can represent a sales channel, geographic region, or line of business. Organizations can have more than one seller, but a seller can have only one organization. and return that result in the Quantity Request API. This feature is useful if you:

  • Sell in multiple countries.
  • Share the same product catalog across multiple countries.
  • Have sourcing restrictions on where order lines can be sourced from based on the seller webstore that originated the order.

Note: If you use this feature, you may want to consider whether or not to set safety stock differently for each Seller. For more information on Seller Level safety stock, see Seller Level Safety Stock in the About Safety StockClosed An additional quantity of an item held in the inventory to reduce the risk that the item will be out of stock. In the context of omni fulfillment, safety stock ensures that not all retail inventory is promised online. and Available to PromiseClosed The quantity of inventory that can be used to fulfill orders on or before a specific date. Inventory topic.

Configuration

To set up ATP by Seller, create the appropriate node groups. Follow these steps.

  1. Review all your nodes and identify which nodes to belong each seller.
  2. Create a node group. Radial recommends using the seller name as the node group name.
  3. Assign all of the nodes that belong to that seller to the node group.
  4. Assign the appropriate Seller Id to the Node GroupClosed A collection of fulfillment nodes.

Example

You have three sellers: Italy, Czech Republic, and Slovakia. To use ATP by Seller, you set up the following three node groups.

Italy: Seller ID TMSEB2

Czech Republic: Seller ID TMSEB3

  • Node 100804- Czech Republic DC
  • Node 100805 - Prague, Czech Republic Store

Slovakia: Seller ID TMSEB4

  • Node 100804 - Czech Republic DC
  • Node 100806 - Bratislava, Slovakia Store
  • Node 100807 - Trnava, Sloakia Store

The following illustration show the setup for the Italy node group.

For an example of how the ATP inventory is calculated, see the ATP by Seller section in About Safety Stock and Available to Promise Inventory.

Best Practices

  • Do not associate the Seller ID field to a Node Group unless you want the Seller to return ATP within the Quantity Request API call.
  • When using Quantity Request API call:
    • By Seller: Assign all nodes that are enabled for availability to a Node Group with a Seller ID.
    • By Inventory Org: Leave the Seller ID field blank on all Node Groups.
  • Although the Status field on the Node Group screen is not active at this time, best practice is to enable the status on this page for all nodes. If you do not want to include a node in the ATP calculations for the seller, then delete it from this page.
  • The Enabled for Availability toggle on the Node Page is the master indicator as to whether the node is included in the ATP calculations. If you want to include a Node in ATP calculations, be sure to activate this toggle.
  • You can have multiple node groups assigned to a single seller. For example, you can have two node groups assigned to one seller for sourcing reasons. You must ensure that the Seller ID is assigned to each of the two node groups.
  • When you add a node after the initial set up, you must ensure that the new node is assigned to the proper node group. If you do not assign it, then that node's inventory is not included in the Quantity Request API response.
  • Seller ID is an optional field. Do not use it for Node Groups if clients are not participating in the Seller Level ATP. In other words, if you are not using Seller Level ATP, then this field should always be blank.

Related Topics Link IconRelated Topics