ASN Integration¶
Advanced Shipment Notifications (ASNs) are generated automatically by Knosc when configured shipment conditions are met, and transmitted to customers via the connected integration. The ASN integration covers both the inbound trigger (detecting when to generate an ASN) and the outbound transmission (sending the ASN to the customer).
Overview¶
Shipment conditions met (gateway stage, BOL entry, or equivalent trigger)
│
▼
Knosc generates ASN automatically
│
├── ASN saved in Procurement → Advanced Shipment Notifications
├── Status set to "Not Sent"
│
▼ [integration job runs, or Send ASNs triggered manually]
ASN transmitted to customer
│
└── Status updated to "Sent"
ASN Generation Trigger¶
ASNs are generated when the configured shipment condition is detected. The exact trigger depends on your integration setup:
| Trigger Type | Example Condition |
|---|---|
| Gateway stage | Order line reaches a configured shipment stage (e.g. stage 5–8) |
| BOL entry | A Bill of Lading number is entered on the order line |
| Manual | User creates the ASN directly in the UI |
Contact your integration administrator to confirm the trigger mapping for your specific ERP or WMS connection.
What Is Included in the ASN¶
Each ASN generated by Knosc includes:
| Field | Value |
|---|---|
| ASN Number | System-generated reference |
| Supplier | Your organisation (you are the supplier sending the ASN) |
| Customer | Customer receiving the goods |
| Ship To | Customer's delivery address |
| Ship Date | Date goods were released from your facility |
| ETA Date | Expected arrival at the customer |
| Lines | One line per item being shipped, with quantity and unit |
| Schedule Agreement ID | Reference to the applicable supplier agreement |
Outbound Transmission¶
Once generated, ASNs are transmitted to customers via the configured outbound channel:
| Channel | Description |
|---|---|
| SFTP | ASN file placed in the customer's designated SFTP directory |
| EDI 856 | Standard ASN document transmitted via EDI connection |
| REST API | ASN data posted to the customer's API endpoint |
| ASN document emailed to the configured recipient |
The transmission channel is configured per customer in Administrator → Settings → Integrations.
ASN Status Flow¶
| Status | Meaning |
|---|---|
| Not Sent | ASN generated but not yet transmitted |
| Sent | Successfully transmitted to customer |
| Accepted | Customer has acknowledged receipt of the ASN |
| Error | Transmission failed - see Notifications for details |
Notifications for Missing Shipments¶
If an order line reaches its expected ship date without an ASN having been generated, Knosc raises an alert in Notifications → Integration → ASN:
- The notification identifies the specific order line
- It includes the expected ship date that was missed
- The notification remains active until an ASN is generated or the order is cancelled
Manual ASN Creation¶
For shipments that occur outside of the automated flow:
- Navigate to Procurement → Advanced Shipment Notifications
- Click New
- Select the associated order
- Enter the Ship Date, ETA Date, and Quantity Shipped per line
- Click Save
- Click Send ASNs to transmit immediately, or wait for the next scheduled run
Error Resolution¶
ASN errors appear in Notifications → Integration → ASN with the specific failure reason:
| Error | Cause | Resolution |
|---|---|---|
| Unknown ship-to address | Ship-to not in Customer Master | Add the address to Customer Master |
| Missing schedule agreement | Agreement ID not found in Supplier Allocation | Add the allocation record or remove the agreement reference |
| Transmission failure | Network or credential error | Check integration credentials in Settings → Integrations |
| Duplicate ASN | ASN already exists for this order line | Review existing ASNs for the order |