Exporting Transfer Orders from Netsuite, and creating Inbound Shipment Plan. It is defaulting the Packing Template to Individual Units. When we create this manually in Amazon, we are using a custom template (see below) because there are 24 units per box. I see that setting the template is not supported via API… I am wondering if this will cause any downstream issues? Printing the labels from Amazon looks correct for the 24 units, but will there be issues when a box holding all 24 units arrives? Any other issues anyone has run into?
Hi Ly,
Thank you for reaching out.
To answer your concern directly it should not. This will not cause downstream issues or receiving errors at the warehouse, as long as your NetSuite TO and skus is configured to show 24 units per box (Case Pack), Celigo transmits that exact ratio to Amazon.
While the Amazon UI uses "Packing Templates" for manual entry convenience, the Celigo Integration App bypasses templates and sends the specific box-level details (dimensions, weight, and units per box) directly from your NetSuite Transfer Order via the API.
Hope this helps.
Hi Raven, This is for the same Shipment TO Addon. Once we successfully create the shipment plan in Amazon, when we run the packing information flow, in Post Packing Information to Amazon Inbound Shipment Plan step, we are running into the below error and it looks like the confirm packing options step is skipped in the flow and unless you open the shipment plan in Amazon UI and confirm the packing options manually and retry the error, the error doesn't go away? Please let me know if we are missing anything to make it work without manually confirming it in Amazon.
"ERROR: Package grouping ID not found in the inbound plan. You can associate a packaging grouping ID with an inbound plan by calling the ConfirmPackingOption operation.",