Amazon Punch Out

We use advanced requisitions (ARM) and have punch outs setup with other suppliers, Grainger, McMaster. However, running into an issue with Amazon around the EDI sent ship to address. Has anyone else been able to use this process? Amazon has been difficult to work with to get this setup.

1 Like

Do you have a fixed set of ship-to addresses (by site and/or warehouse)? Amazon may have a spot in their portal where you can create the ship-to locations and assign a unique code (site, site+warehouse, etc). That code would then have to be sent to Amazon on your 850, likely in element N104 with an ST qualifier.

We don’t do outbound 850s with Amazon, but we do have vendor EDI partners. We’re sending 850/POs not only for ship-to sites…but also to our customers warehouses via dropship. We usually combine CustID and ShipToNum as the unique ID for those.

So you’d need to fill element N1/04 (qualified by ST) something like this:
Case if CustShipTo=‘’ then SiteID else CustShipTo

1 Like

ARM is Company/Warehouse combinations. The information for the EDI is sent as cXML format, not a standard EDI format. I know when we’ve setup other ones that it also depends on what the system on the other end can handle. Some required fixed information.

If you’ve got a fixed list of company/warehouse combos then they may need to be loaded at Amazon before the orders can go through via either protocol (formal EDI or cXML). I can’t speak to their Punch Out portal setup though…sorry.

If they’re validating ship-to codes, that also likely means they can’t handle one-time shipment addresses for your POs. We have the same issue on the customer side. Our inbound maps are “either/or”…validate on N1/ST/04, or process as OTS.

Thank you for the feedback.

On additional testing and suggestion from Precise, Amazon’s punch out does not support ship to addresses on lines. So once I removed the xml code for the ship to against the individual lines it worked.

2 Likes

Glad to hear it. From an EDI standpoint, most of our customers and vendors take ship-to’s only at the order header level and not at line level.

Every once in a while you’ll find someone that uses the SDQ segment at the line level that allows multiple ship-to locations/quantities for a single line item (i.e. 500 widgets - 200 to location A, 250 to location B, 50 to location C).