Tronix Login

321 STRONG · Tronix

Sign in with Google

Access restricted to @321strong.com and @quietmine.com emails

or

π Supply Chain
Admin Logout
Tronix/Supply Chain/Hub

Hub

Data as of —
PO → Shipments → Warehouse → AWD → FBA

Where every unit is — every SKU, broken by family

…
Loading…

Feeding Crons

Loading cron status…

Data Provenance

Click a card for the full provenance detail.

SOURCE⤢fba_snapshot (daily)`tronix-sync-fba` (SP-APIgetInventorySummari…SOURCE⤢awd_inventory (daily)`tronix-sync-awd` (SP-API AWDlistInventory,…warehouse_inventory + overrides (NO CRON) — Hand-counted sheet mirror plus B's durable override, which wins (#14002). Refreshed only by an on-demand import — and UNRECONCILED against AWD, so in-transit units can sit in both columns until B re-counts.SOURCE⤢warehouse_inventory + ove…Hand-counted sheet mirror plus B'sdurable ov…purchase_order_items ⋈ purchase_orders — Native in-app PO creation. `getPoStageQtyByAsinSku()` derives `PO > Unshipped` as open PO qty minus everything shipped against those POs — there is no stored field for it.SOURCE⤢purchase_order_items ⋈ pu…Native in-app PO creation.`getPoStageQtyByAs…shipments ⋈ shipment_items (AWD only) — B: "shipments is awd shipments, which is po days totalling participatory" — a shipment is a PO in flight to AWD, filtered to shipment_type = awd_inbound and the four in-flight states, net of units already received. Its units stay inside Total > PO; there is deliberately no Total > Shipments.SOURCE⤢shipments ⋈ shipment_item…B: "shipments is awd shipments, which ispo d…dim_asin.stickers (FROZEN — no producer) — `tronix-import-stickers` was permanently DELETED (#15336, B's call 2026-08-07), so this column has NO producer and its counts are frozen at their last import. B accepts this — an "order stickers" button on the Stickers wedge is coming as separate work. Do NOT file a staleness ticket and do NOT restore the importer to unfreeze it. Sticker stock is not product inventory and is in no unit total. Presented as stale, never as live.SOURCE⤢dim_asin.stickers (FROZEN…`tronix-import-stickers` was permanentlyDELE…TRANCHE_ADDITIVE → rollUpLocationPosition() — Which columns may sum with which is DECLARED ONCE, in src/lib/tronix-supply-pool.ts, and the endpoint and the table both read that declaration rather than each keeping a list — it is also what decides which columns get their stage's font colour. Every subtotal still carries its own independent check delta, four of them, on the payload: #15318 removed the Δ CHIP from the screen, not the computation, because a silent invariant is what let four surfaces drift apart originally.PIPELINE⤢TRANCHE_ADDITIVE → rollUp…Which columns may sum with which isDECLARED…STORE⤢tronix.db (read)fba_snapshot ⋈ awd_inventory ⋈warehouse_inve…VIEW⤢This View/admin/tronix/supply-chain — one row perACTI…

Docs & References

Agent Brief
docs/tronix/wedges/supply-chain.md
References
None.

Edit agent brief — docs/tronix/wedges/supply-chain.md

Markdown. Saved to the DB (wedge_docs) live — no deploy. This is the brief handed to dispatched agents.

Source freshness

Loading…

Can a unit be in two columns?

Constantly — which is why only the columns listed in TRANCHE_ADDITIVE enter a subtotal, and why only those columns carry their stage’s font colour. The rule that settles every case: in-flight stock belongs to the stage it LEFT. So AWD Inbound sits inside Total PO (it left the PO, it has not landed), AWD Outbound is additive at AWD, and the three FBA Inbound legs render uncoloured. The overlaps that rule does NOT close:
Saved successfully!
Something went wrong