Skip to main content

Why can’t I create or send an ASN to my warehouse, and how do I fix it?

“Send shipment” appears in a supply shipment’s More actions menu only when its destination is a building whose fulfillment integration is a warehouse integration: Extensiv, Fuse, GoBolt, InfoPlus, Jazz, MasonHub, Mintsoft, ShipBob, or Veracore. It is missing when the shipment has no destination or a custom destination, when the building has no such integration, or when that integration is archived. Set the destination building on the Destination & Route card.

Sending runs in the background. Check the shipment’s Activity tab for the result. A successful send adds the “Sent to WMS” badge. Sending fails when:

  • the shipment is Closed or Canceled
  • it has no items
  • its building has no warehouse integration
  • for Veracore, the integration has no System ID, or the shipment has no Expected Arrival Date
  • the warehouse rejects it, for example for a missing product. The Activity tab shows the warehouse’s message.

Fix the cause and choose “Send shipment” again. A shipment that was already accepted is not sent again.

For a Shipfusion building, create the ASN in Shipfusion directly. Contact Endless support for help sending ASNs to Shipfusion.

Errors when you create or save a supply shipment come from its own rules: a shipment number of up to 50 characters, a tracking number of up to 100, either a building or a custom destination, an active location inside the chosen building, a quantity above 0 on each item, and an SKU that matches the linked purchase order line. The message names the rule that failed.

“Unable to generate a unique PO number for ASN” comes from GoBolt. Endless sends the shipment number as GoBolt’s reference. If GoBolt already has it, Endless tries the number with -1 through -4 added, and stops when all five are taken. Change the shipment number to one GoBolt has not used, then send again.