Operations
From sale sign-up to checked prices
The agent checks sale prices, builds the daily flash and drafts listings. People change prices and pause products.

Where work stalls
- 01
Before a sale, every promotional price has to be checked, and one miscalculated net price after stacked discounts becomes a direct loss.
- 02
Daily numbers are exported from each storefront and the inventory system and stitched together, so anomalies only show once the report is done.
- 03
Return reasons and negative reviews are scattered across channels, so a batch quality problem is confirmed only after returns pile up.
Work agents take on
01 / 04
Sale price check
The day before submissions close
The holiday sale sheet is in the promotions folder. Work out the net price for every variant after the HOLIDAY10 code, and flag anything below our price floor, any sale price below MAP and anything without enough stock to last the sale. Submissions close at 6pm tomorrow
- Holiday_sale_variants.csv
- Sales_last_30_days.csv
- Ops · Promo rules
- Ops · Price floors and MAP
- Inventory (HTTP plugin, read-only)
- Turn the promo rules into price and stock checks
- Compute every variant's net price after codes and discounts in code
- Compare against floor, MAP and days of cover, citing the rule for each flag
- Resolve each flagged row, with anything below floor also needing financeE-commerce lead Tom Becker
- Generate the import file for the team to upload in the store admin
Every step is in the run trace

Where people decide
Agents prepare the work. Key decisions stay with people.
- 01
The e-commerce lead resolves each flagged price, and anything below the floor needs finance's sign-off
- 02
Restocking, pausing a product or contacting a supplier is the owner's decision, and the agent lists the evidence
- 03
Certifications and product claims in a listing are confirmed by brand or legal











