There are four order types that come through on a purchase order: RPC1, RPC2, RPC3, and RPC4
RPC1/RPC2 = stock replenishment orders. You'll notice that the PartnerSKU on the order ends in STOCK.
RPC3/RPC4 = customer drop ship orders. You'll notice that that Partner SKU on each order ends in CWO.
Based on the order type, there are slightly different rules on shipping/invoicing:
For RPC1 and RPC2, partial quantity shipment is allowed (at the line level). Since these are stock replenishment orders, partial quantity shipments are acceptable because the impact to the customer is limited.
For example: Line 1 has 100 pieces of PartnerSKU ABC123STOCK, Line 2 has 80 pieces of PartnerSKU XYZ987STOCK. However, only 75 pieces of Line 1 can be filled (Line 2 can be filled in its entirety).
- For Line 1, ship 75 (of the 100 pieces ordered) for ABC123STOCK
- For Line 2, ship 80 (of the 80 pieces ordered) for XYZ987STOCK
- Backorder the remaining quantity of Line 1 (via a PO Acknowledgement) 25 (of 100 pieces ordered) for ABC123STOCK, along with an expected ship date.
For RPC3 and RPC4, ship only the ordered quantity. Since these are customer orders, partial quantity shipments could negatively impact the customer. On a multi-line order, you can ship the lines that are available, but only the full order quantity.
For example: Line 1 has 5 pieces of PartnerSKU DEF123CWO, Line 2 has 10 pieces of PartnerSKU MNO123CWO. However, only quantity 8 is available for Line 2 MNO123CWO (Line 1 can be filled in its entirety).
- For Line 1, ship 5 (of the 5 pieces ordered) for DEF123CWO
- For Line 2, do NOT ship 8 (of the 10 pieces ordered) for MNO123CWO. Instead...
- Backorder Line 2 (via a PO Acknowledgement) 10 (of 10 pieces ordered) for MNO123CWO, along with an expected ship date. Once all quantity is back in stock, ship the entire line.
Depending on the communication method, here is the best way to identify the order type:
- EDI (segment): REF*MR*RPC3~
- XML (field): <Name>MRCode</Name>
- JSON (field): "Name": "MR_Code"
- CSV (header): OrderLine.ExtendedAttribute.MR_Code
- Portal: The easiest way for Portal is to look at the PartnerSKU. If it ends in STOCK, that is RPC1 & RPC2. If it ends in CWO, that is RPC3 & RPC4.
Comments
0 comments
Article is closed for comments.