Porto Textiles moved run 02 on PO-2408
Evidence
Run 02 · 800 units changed from Sep 25 to Sep 28.
Sep 25Sep 28
Activity
- Read the source
- Connect the record
- Apply your workflow rules
- Update the record & follow up
AmberOS drafts a purchase order straight from an awarded quote with costs and duties already attached, then reads your supplier's email to keep the order current without anyone re-typing a status.
A module of AmberOSWatch Amber match a supplier invoice, catch a price difference, and close the task once the corrected invoice matches.
| Article | HTS | Quantity | Subtotal | Category | Status | Unit cost |
|---|---|---|---|---|---|---|
| Radiance Vitamin C Serum 30 mlVC030 | 3304.99.50 | 6,000 | USD 67,200.00 | Skincare | Active | USD 11.20 |
| Barrier Repair Moisturizer 50 mlBR050 | 3304.99.50 | 5,400 | USD 53,190.00 | Skincare | Active | USD 9.85 |
Unit costs and estimated duties are already on every SKU when the draft opens.
Payment schedule matches your real terms with the factory, not a generic default.
Internal sign off and factory confirmation happen in the same record, not two separate systems.
“The second run needs three more days. First run is on schedule.”Porto Textiles · Supplier email
One purchase order fans into multiple production runs and allocations, each with its own dates.
Not per order. Shipments split and clear customs separately, and the duty math follows the goods.
Shipping status is calculated from what actually shipped, never from a field someone forgot to update.
Production runs and allocations
In progressDuties calculated per leg
Status computed, never remembered
Production updates, revised dates, and partial shipments land on the record automatically.
Everything that matches the plan clears itself. You see the exceptions, not the noise.
Reads the supplier email thread
In progressFlags only what does not match
AmberOS chases specific orders and products by email, reads the replies, and updates the record automatically. Fewer days spent hunting for a status update.
Meet your Digital WorkerRun 02 · 800 units changed from Sep 25 to Sep 28.
Sep 25Sep 28
Illustrative data. No message is sent.
Frequently asked questions
Yes. Orders split into production runs, allocations, and legs, each tracked with its own dates and duties.
No. Status is computed from the shipments attached to the order, not typed in by hand.
It lands on the record from the email update. The exceptions inbox flags the quantity difference so you can accept it or act on it.

See how the whole workflow comes together with the Amber team.
Shopify is to sell. AmberOS is to source, make, and ship.