Procurement & PO Automation

ERP-to-Project-Board Purchase Order Sync

POs now flow into a shared master board with classification, split-destination subitems, warehouse routing, normalized dates, and duplicate-safe updates. The workflow reduced...

4 production workflow fixes
Recurring PO data issues resolved
~15 min to ~1 min
Board setup time reduced
~2-8 seconds
Processing speed per PO
One master board for Tour Ops and Ecommerce
Shared tracking model
The problem

Every purchase order created in the ERP had to be re-keyed by hand into a Monday.com board so the Tour Ops and Ecommerce teams could track it. A person opened each PO, read the vendor, artist, dates, SKUs, quantities and split-shipment details, typed it into the board, decided which warehouse it should ship from, and repeated that for every split destination, slow, easy to get wrong, and prone to dates landing in past years. The two teams used different status terminology, so the data drifted.

System designed

Mapped the PO lifecycle from ERP creation to team tracking, warehouse routing, split-shipment handling, and status normalization. The workflow creates one shared operating board where Tour Ops and Ecommerce can see the same PO record, shipment splits, warehouse destination, dates, and item details without duplicating entry across systems.

Outcome

POs now flow into a shared master board with classification, split-destination subitems, warehouse routing, normalized dates, and duplicate-safe updates. The workflow reduced board setup work from roughly 15 minutes to about 1 minute and eliminated several recurring sources of bad PO data, including wrong-year dates and inconsistent shipment routing.

Proof to show

Warehouse-routing decision tree beside a redacted before/after view of the master PO board.