Audience: All users in Logicbroker.
In this article, you will find information related to Orders. The sections within this article are outlined below:
- Overview
- Order Document
- Sales Orders and Purchase Orders
- Order Routing
- Order Rerouting
- Order Workflows
- Download Packing Slips
Overview
Logicbroker identifies an Order (EDI 850) as any sales order or purchase order (PO). Orders initiate the order lifecycle and will continually update until order items are fulfilled (and invoiced). Logicbroker uses sales orders to create purchase orders to send to suppliers.
Retailers and suppliers send/receive order information depending on how they are integrated with Logicbroker (EDI, API, JSON, XML, CSV, Flat File, Logicbroker Portal).
Order Flow
-
- Customer places an order on the retailer’s eCommerce site
- The order is sent to Logicbroker
- Logicbroker transforms the data to a format the supplier accepts
- Logicbroker sends the order to the supplier
Order Document
From the portal, users can see documents regardless of the way they are integrated with our system. To see document details, search for it using the search bar, click on it from the Dashboard or click View on the Orders page. See the order document-specific details below. For general document information, see our Documents article.
Sales Orders and Purchase Orders
In the portal, retailers will see the sales order come in with the Order ID from their system and it will show the Sender and Receiver fields as the retailer company. This document will go to Complete once the Purchase Orders (Pos) are created and sent to the corresponding suppliers.
Sales Orders come in with the Order ID. In Logicbroker, we note this as the Reference Number. When creating the Purchase Order, we will attach the prefix PO to the Reference Number and add the suffix of -001 to the end. If a Sales Order is being split between multiple suppliers, the suffix will follow the -001, -002, etc. format.
Order Routing
Retailers have a few different options for order sourcing. These are implemented through a workflow that runs on every sales order to route item data to appropriate suppliers based on rules set. Logicbroker will work with retailers during the integration process to confirm and implement order sourcing preferences.
Routing by SKU will source sales orders based on SKUs tied to specific suppliers. Logicbroker will look at each item on the sales order and identify which suppliers carry the product. Once determined, we will create a purchase order that goes out to that specific supplier to have it fulfilled. A Matching File matching supplier SKUs to merchant SKUs is required for this process to work.
Routing by cost will source sales orders based on cost and supplier. Logicbroker will look at every item on the sales order and identify which suppliers carry the product. Once identified, we will check which of the suppliers have the product available (checking against their latest inventory feed). Once all possible suppliers have been identified, we will compare costs as well as compactness for all available suppliers and send the appropriate quantities on a purchase order to the supplier(s) with the most competitive pricing as well as with the most compact score. Please note: Suppliers that have not updated inventory since time of item allocation will not be considered since feeds will reflect 0 quantity regardless of actual feed quantities
Compactness is scored using the following data points:
-
- Quantity
- Cost
- Fewest Suppliers
- Highest “Score” based on Logicbroker’s algorithm
Order Rerouting
Retailers can reroute orders in the case where a vendor is unable to ship out a product and multiple vendors offer the same product.
- Retailer must rerouting on the sales order, not the purchase order
- Retailer must have partner sourcing, not SKU sourcing
- Retailer must send the primaryvendor ID on the order
- Partially shipped orders cannot be rerouted
- Status is Shipped: you cannot reroute the line
- Status is Cancelled or Ignored: you can reroute the line but no cancellation acknowledgement will be created
- Status is Ready to Acknowledge or Ready to Ship: you can reroute the line and a cancellation acknwoledgement will be created
Order Workflows
Logicbroker provides a variety of workflow options that can be used for a variety of reasons. These would need to be established between supplier/retailers and your Logicbroker account manager during the integration process where our team will work to implement and test changes. In order to have workflows added to your account, you must be an active Logicbroker customer.
In some cases, suppliers may need custom SKU mappings if the retailer sends a SKU value on the order that does not match to the SKU the supplier has in their system. Logicbroker can do a lookup on the SKU that the retailer provides on the order sand them map it to the value needed to be sent to the supplier’s system. We will save the incoming SKU and ensure it is sent back to the retailer the way it was received.
This workflow is set up on the supplier side.
Retailers working with replenishment integrations may find it necessary to send orders to multiple ship-to locations. Logicbroker can identify different store/DC locations and generate sub-Pos for each so they can be easily identified and packaged by the respective warehouse.
This workflow is set up on the retailer side.
Many retailers will send an address code on the order and expect suppliers to map the correct ship-to address. Logicbroker can map address codes to ship-to addresses and send addresses on orders to the supplier so no mapping needs to happen in their system.
This process allows the cost of each item on an order to be updated using the cost on latest received inventory feed from a supplier. This allows for more accurate invoicing later during the order life cycle.
This workflow is set up on either the supplier or retailer side.
This workflow allows order data (can be used for other documents as well) to be transferred between more than 2 companies using a format that specific system accepts. This is useful for a 3PL-type flow, or if there is another system that needs to receive transaction data, after it has already been communicated between 2 different companies. Once an order is received, the workflow triggers based on the document sender and receiver and exports all the data to an additional company and/or entity.
This workflow is set up on either the supplier or retailer side.
Download Packing Slips
Suppliers can download packing slips off order documents for review or to print on an order level. Downloading packing slips off orders will reflect order level information meaning that all order items will show regardless of shipping status. For more information on downloading packing slips in bulk or off shipments, see our Bulk Actions article or our Shipments article.
Comments
Please sign in to leave a comment.