ForceGet & ERP Import
Upload weekly CSV exports — ForceGet Shipments, Duty Invoices, Container Costs, and goodday ERP Purchase Orders. Each importer is idempotent, so re-uploading the same file updates existing records instead of duplicating.
Sync Goodday POs
Refresh purchase order data directly from goodday's ERP without exporting a CSV. Recommended over the CSV importer below — richer schema, no column-mapping maintenance, propagates SKUs to shipments automatically.
How to sync
- Ask Claude in the Cowork chat for a fresh goodday PO payload. Say something like: “Give me a fresh goodday-payload.json”. Claude pulls the current PO lines from goodday's MCP data warehouse and writes the JSON to your Cowork workspace folder as
goodday-payload.json. - Drop the file here using the “Upload JSON” button below, or open the file in a text editor and paste its contents into the box.
- Click “Sync now”. The sync runs in a few seconds and reports the results inline — how many lines were upserted, how many FGET# containers got their SKUs propagated, and any unmatched FGETs (usually shipments ForceGet hasn't ingested yet).
Recommended cadence: run this every Sunday morning before the noon-PST refresh cron kicks off, so the team's Monday summary reflects the latest PO status. You can also run it mid-week any time — the sync is idempotent, safe to re-run on the same payload.
or paste below
1. Shipments
Export from
Shipment > Shipment List in ForceGet. SKU is auto-inferred from supplier part numbers (FRB-13M → Solara-Pro, JYS-3B → Steamkit-V1, Wildland → Pulse-Pro) or unit count. Idempotent on FGET#.Expected columns (any of): FGET#, Container Number, Supplier, Departure Date, ETA Port, ETA Final, Status, Destination Code, Part Number / SKU, Units, COGS per Unit, COGS Value
2. Duty Invoices
Export from
Billing > All Invoices filtered by Duty type. Idempotent on invoice number (DT-XXXXX). Invoices for unimported shipments are stored without a shipment link — re-import shipments first to fix.Expected columns (any of): Invoice Number, FGET#, Amount, Status, Invoice Date, Due Date, Paid Date
3. Container Costs
Export from
Billing > All Invoices filtered by Shipping / Drayage type. Used for variance dashboard actuals — overseas freight + inbounding per container, replacing the $8,500 / $1,100 defaults. Idempotent on FGET#.Expected columns (any of): FGET#, Overseas Shipping, Inbounding, Arrived At
4. Purchase Orders (goodday ERP)
Export PO lines directly from goodday — the importer reads goodday's native column names verbatim, no editing required. Linkage to ForceGet shipments comes from the
Shipper Reference ID column (e.g. FGET-81314). Multi-shipment cells like FGET-80222/23/24/25 are split and propagated to all linked containers. Idempotent on (PO Number, Block Number, SKU).Expected columns (any of): PO Number, Block Number, SKU, Vendor Name, Current Units, Vendor Cost, Extended Price, Est. Landed Cost, Duty Rate, Duties, HTS, COO, Incoterms, ETA Date, PO Date, Shipper Reference ID, PO Status, Inventory Status, Received Units, Vendor Invoice Number