Imported valve assembly
Entry `123-4567890-1`, SKU `VALVE-88`, China origin, 1,200 units, ordinary duty plus Section 301 duty split into separate fields.
Synthetic example
What a customer might send over first.
A useful first share is usually not a perfect claim packet. It is a small set of exports from the broker portal, ERP, WMS, freight system, and BOM module that lets the screen test whether import/export records can be matched.
Likely files
The practical first-share packet.
What each file proves
The screen is looking for record traceability, not a refund promise.
- Broker import entry lines: entry number, import date, SKU, HTS, origin, quantity, value, and duty categories.
- Export shipment history: export date, SKU, quantity, destination, and BOL/AWB/AES or shipment reference.
- BOM component map: finished SKU to imported component SKU when exported products are assembled from imported inputs.
- Source inventory: system, owner, export date, received date, covered period, and version notes for each source file.
Example rows
What the records look like in plain English.
Exported unused valves
Shipment `BOL-MX-7701`, SKU `VALVE-88`, 320 units to Mexico, creating an exact-SKU match and a Canada/Mexico review flag.
Finished pump skid
Exported SKU `PUMP-SKID-A` maps to imported components `MTR-240`, `CTRL-12`, and `STEEL-BRKT-77` through the BOM.
Expected output
What this synthetic packet produces.
- Exact SKU unused-potential matches.
- Manufacturing-potential matches through BOM rows.
- Excluded-duty flags for Section 232 and AD/CVD amounts.
- Canada/Mexico export flags for licensed broker review.
- One deliberate data gap for an exported SKU with no matching import or BOM path.
Boundary
This is a synthetic teaching packet.
These files are not real client data and do not prove refund eligibility. They show the shape of the records needed for a first-pass data screen before any licensed broker, drawback specialist, or trade counsel review.