Price Edit

Price Edit is where a price change is modelled before it is made. A draft holds as many products as you like, prices them in a spreadsheet, and shows the margin each new price earns. Nothing reaches the marketplace until you deploy on the last step, so a draft is always safe to open, edit and abandon.

The five steps

1. Create Draft — from scratch, or from a commission change with margin-keeping prices already filled in.
2. Choose products — pick the variants this draft covers. You can add more at any point.
3. Settings — on a commission draft, choose whether to protect each product's margin or its profit, the smallest discount you're willing to keep, and any buffer above the margin-keeping price. Edits you make by hand afterwards still win.
4. Edit Price — the sheet. Type a new price and that row's margin, profit and tier prices recalculate.
5. Deploy to platform — review what actually changed, then send it.

Where you are in the draft lives in the address bar, so a refresh, a Back, or a pasted link reopens exactly where you left off.

The sheet

• Layout — horizontal puts one row per product with price, margin and profit side by side; vertical stacks one row per metric so more price groups fit on screen. Neither changes a price.
• Filters — negative margin, below the margin floor, needs whitelist, changed only. Scope them to the page or the whole draft.
• Sheets — split a large draft into tabs, rename them, and move a selection from one to another.
• Undo / redo and decimal places. Decimals are display only: the price that deploys is unrounded whatever the sheet shows.
• Download Excel / Upload Excel — the round-trip. The file carries id, product, sku, current_price, new_price, new_margin_pct, new_profit and one column per tier. On the way back in, only the id and the new price are read — everything else is recomputed live, so a stale margin in the file can never overwrite a real one.
• Rows without margin stay blank rather than showing a figure that ignores marketplace fees. Those variants have no cost or fee data yet.

How a row is identified

The Product column holds the listing's name, and a SKU column sits beside it. Both stay pinned when you scroll right, so a row never loses its identity out at the tier columns. The sheet's find box matches on product name, variant name or SKU.

That SKU is the marketplace's — the variant SKU, falling back to the product SKU. Where you never filled one in Seller Center, the column shows the product's DataGlass nickname instead, so a row is never left with only a title. The nickname is your own name for the variant, set on the product in DataGlass; the SKU wins whenever the listing has both, because that is the number Seller Center reconciles against.

The column disappears entirely on a draft where no product has either.

Both travel with the file. The Excel export carries sku and nickname as their own columns, and so does the draft's XLSX download.

Deploying

The draft's status tells you exactly how far a change has travelled:

• Draft — still being edited, nothing sent.
• Needs whitelist — some products' list prices go up, which the platform must approve first. See Price increase whitelist.
• Ready — reviewed and deployable.
• Scheduled — queued to deploy at the time you picked.
• Deployed — live in your shop.
• Partially applied — some prices are live and some are not; reopen to see which failed.
• Failed — nothing was applied. Fix the reported rows and deploy again.
• Rolled back — the previous prices were restored, so nothing from this draft is live.

Every deploy this shop has made, including the rows the platform refused, is kept in History.