A read-only example of how MarginMining turns import documents into a founder-led review, with supplier and carrier clearance follow-ups only where they add certainty.
MarginMining helps prepare review questions from shipment evidence. It is not customs, tax or legal advice.
Potential duty review opportunity. Based on duty charged on the clearance invoice for this shipment.
Moderate confidence · Confidence reflects the evidence on file. It becomes stronger once the import declaration is added.
These are the shipment files used in this sample Import Review.
Commercial invoice
Supplier invoice with line values and currency for the shipment under review.
Packing list
Carton counts and SKU quantities used to check allocation basis.
Clearance invoice
Carrier clearance charges captured, but categories need clearer allocation.
Import declaration
Not provided. Duty and GST cannot be checked from the evidence yet.
Certificate or declaration of origin
Not required to run the review, but helps confirm origin-related notes on the invoice.
Supplier SKU or product list
Supplier SKUs and store SKUs need mapping before Landed COGS is exported.
Short questions raised from the evidence so it is clear what to check and who to ask.
The supplier invoice and packing list are on file, so the shipment can be reviewed now without waiting on external follow-up.
Review logic
Landed cost review · HS code and origin evidence
Freight and fixed shipment charges need a consistent allocation basis before Landed COGS is exported.
Review logic
Landed cost review · Allocation basis
Supplier SKUs and store SKUs need mapping so costs land on the right product.
Review logic
SKU mapping review · Landed COGS readiness
DHL, FedEx, UPS or your freight forwarder can supply this so duty and GST paid can be confirmed against the invoice.
Review logic
Import declaration checks · Duty and GST evidence
Once the declaration is on file, the duty and GST basis can be reconciled against the invoice.
Review logic
Import declaration checks · Duty and GST evidence
Recipient-owned actions generated from the evidence, grouped so it is clear who to ask next.
Duty treatment sits directly on your landed cost. Reviewing HS code and origin coverage against the supplier documents now protects margin before costs move into your store.
Review logicLanded cost review · Missing: Import declaration, Origin declaration (helpful)
The import declaration confirms the duty and GST actually paid so it can be reconciled against the supplier invoice.
Review logicClearance team question · Missing: Import declaration, Duty calculation +1 more
Sendable request available in the Sendable evidence requests section.
The packing list on file is the basis for allocation checks. Confirm with the supplier only if quantities look inconsistent with the invoice.
Review logicSupplier question · Missing: Packing list, Carton count +1 more
Sendable request available in the Sendable evidence requests section.
Freight, clearance and fixed shipment charges need a consistent allocation basis so landed cost is comparable across SKUs before it is used for pricing.
Review logicLanded cost review · Missing: Allocation method, Shipment level charge breakdown
Sendable request available in the Sendable evidence requests section.
Landed cost only helps margin decisions if it lands on the right product. Mapping supplier SKUs to store SKUs now avoids costs being applied to the wrong variant.
Review logicLanded cost review · Missing: Supplier SKU, Store SKU +1 more
Sendable request available in the Sendable evidence requests section.
This sample has enough evidence to prepare questions, but the landed-cost export still needs review before costs are used downstream.
Review Landed COGS checks before relying on these costs.
This sample shows how MarginMining prepares review questions from shipment evidence. It is not customs, tax or legal advice.
Upload the documents you already have. MarginMining will show what is missing, what to question and who to ask next.