Examples: see what the checks catch
This read-only example uses invented data. No account, file upload, AI call or company record is created.
Invoice
SKU BRACKET-01 · 24 pieces · $10 each · $240
Packing list
2 cartons × 10 pieces = 20 pieces
Needs review
Invoice 24; packed 20; difference 4 pieces. Confirm the actual shipment before changing either document. Approval must apply to the corrected version.
For the next repeat order
Store an approved specification: SKU, HS/origin, pieces per carton, net/gross weight and dimensions. A full-carton structured order can reuse it. Partial cartons, conflicting variants, refunds, dangerous goods and missing lot data need attention.
Frozen seafood supports glaze percentage in gross-weight checks; net weight is declared without glaze. This is a document calculation, not a health certificate or a complete seafood compliance service.
Lot and expiry checks are already included
Invented example: the invoice lists LOT-A, while the packing line lists LOT-B for the same SKU. The mismatch needs correction. Conflicting expiry dates within one SKU/lot also need review. This does not verify a pharmaceutical licence or supply-chain certificate.
Glaze and tare: a concrete calculation
Invented example: 10 kg net seafood, 20% glaze, 2 cartons at 0.2 kg tare each. Expected gross = 10 ÷ 0.8 + 2 × 0.2 = 12.9 kg. Enter the actual product and carton values; do not copy these example values into a shipment.
Set components: a concrete check
Invented example: 10 sets, 2 mugs per set. Expected: 20 mugs. Packed: 19 mugs. One mug is missing; final documents are blocked until corrected. The component list adds no invoice value or carton weight.
You can reopen saved work
Saved shipment data can be reopened. Its revision history shows changed business fields, before/after values, person and time. Editing invalidates the old approval. Review save/error indicators before leaving the page; an offline connection is not a completed save.
Scope you can evaluate
Export-document preparation and consistency checks for supported workflows. The US/UK focus describes the initial exporter markets. Examples include other destinations; destination-specific legal documents still need your specialist or forwarder.
QuickBooks/Xero are accounting connections. They are not native SAP, NetSuite, CargoWise, Oracle or Dynamics integrations. Those systems require a vendor-specific bridge. ECCN/licensing, restricted-party screening, USMCA eligibility, CITES and signed dangerous-goods declarations are outside the current product scope.