Supplier to HAWB flow
Suppliers create consignments. Consolidators/Exporters group them into MAWB shipments, turning each consignment into a HAWB.
ASN
System Guide
ChopChop ASN and ASNscan
User and system guide for Exporters and Handling Agents
Use this guide to understand what ChopChop ASN can do, which company roles are involved, and how freight moves from expected records into scanned receiving outcomes.
Company-aware access
Exporter users see their ASNs. Handling Agent users see ASNs assigned to their company. Admins can oversee the full operation.
Consignments and pieces
ASN lists should show consignment count and total physical pieces so teams can understand workload at a glance.
Live receiving workflow
ASNscan records scanned pieces, tracks received counts, and can support live dashboard updates as pieces arrive.
Operational traceability
Every ASN keeps clear ownership, handling responsibility, status, exceptions, scan timestamps, and user attribution.
What ChopChop ASN Does
ChopChop ASN helps Exporters and Handling Agents agree what freight is expected, who is responsible for handling it, and what has physically arrived.
An ASN has a permanent internal system ID, plus a user-facing ASN Reference. In many workflows the ASN Reference is the MAWB or another operational reference that users import, search, and scan.
Supplier Consignments
Suppliers create consignments before export. A supplier consignment contains receiver details, goods details, parcel pieces, and labels generated under the supplier account.
Supplier consignments are not MAWB shipments yet. They are freight records waiting to be accepted or grouped by a Consolidator or Exporter.
Consolidator / Exporter Workflow
Some Exporters are also Consolidators. They invite Suppliers, review approved supplier consignments, and build MAWB shipments for export.
When a consignment is linked into a MAWB shipment, ChopChop treats that consignment as a HAWB inside the export shipment.
Exporter Company
The Exporter Company owns or creates the ASN. It provides the expected freight details and assigns the ASN to a Handling Agent when the handling work will be done by another company.
Exporter users need to see which Handling Agent is responsible, the number of consignments, total pieces, scan progress, exceptions, and status.
Handling Agent
The Handling Agent receives, scans, sorts, deconsolidates, and distributes the freight. A single Handling Agent may process ASNs for several Exporters.
Handling Agent users need the Exporter shown clearly on each ASN so they know whose freight they are processing.
Internal and External Parties
Both sides can be ChopChop companies or external parties recorded by name. ChopChop supports Exporter to Handling Agent, external Exporter to ChopChop Handling Agent, ChopChop Exporter to external Handling Agent, and record-only external-to-external cases.
External parties do not receive login access unless they are invited later. Their names are still recorded so responsibility and reporting remain clear.
ASNscan Receiving
ASNscan is used by the Handling Agent during receiving. Operators load the ASN Reference, then scan each arriving parcel or piece.
Repeated scans of the same piece reference can be valid when several physical parcels share the same barcode or tracking number. Scans count up to the expected piece count; scans beyond that become over-scans.
Status and Exceptions
ASN status should describe the receiving state: Open, Receiving, Partially Received, Received, Exception, Closed, or Cancelled.
Exceptions include over-scans, unexpected pieces, missing pieces, mismatches, or scans under the wrong ASN.