Schedule market and price-list changes with Rollouts
Stage a set of market and price-list changes — a sale's pricing, a market going live, a currency, tax or return override — and apply them immediately or at a scheduled time.
On this page
You need the same settings access as Markets. Rollouts change markets and price lists that already exist in your store; it doesn't create new ones.
Open Rollouts
Go to Markets → Rollouts to see every rollout for this store, newest first, with a status filter (Draft, Scheduled, Applied, Canceled).
Create a rollout
Click Create rollout, give it a name, and add changes as setting keys and values — for example a market's status, its currency, catalogs, taxes or returns customization, or a price list's adjustment type or value.
- markets.<id>.status — "active" or "draft"
- markets.<id>.customizations.<currency|catalogs|taxes|returns> — the same values the market editor accepts, or null to revert it
- price_lists.<id>.adjust_type — "percent" or "fixed"
- price_lists.<id>.adjust_value — a whole number (basis points for percent, cents for fixed)
Review before applying
Each change is validated with the same rules as the Markets and Catalogs editors — an invalid value, or an id that isn't one of this store's own markets or price lists, is refused with a specific error next to that change, and nothing in the rollout applies until every change in it is valid.
Apply now, or schedule it
Choose Apply now to write every change immediately, or set a Schedule time to apply it automatically later. A scheduled rollout applies itself within about a minute of that time — you don't need to be signed in when it runs.
See what each change replaces
Once applied, the rollout's detail view shows "was …" with the previous value next to each change, so you can see exactly what it replaced.
Handle a schedule-or-cancel conflict
If a scheduled rollout already applied by the time you try to reschedule or cancel it, Lulu refuses the request and shows its real current status instead of silently overwriting it — reload the rollout and decide from there.
Know the retry behavior
If an automatic apply fails, Lulu retries it up to 3 times before giving up and recording the error on the rollout.
CHECK YOUR WORK
You’re ready when…
- Used setting keys the rollout understands (market status, market currency/catalogs/taxes/returns, or a price list's adjustment type/value)
- Reviewed every change for an error before applying
- Chosen Apply now for an immediate change, or set a Schedule time for later
- Checked back after a scheduled time passed to confirm it actually applied
IF SOMETHING DOESN’T LOOK RIGHT
Troubleshooting
My rollout shows an error instead of applying.
Each change key is validated before anything is written — an unsupported key, an invalid value, or an id that doesn't belong to one of this store's markets or price lists is listed as an error next to that change, and nothing in the rollout applies until every change is valid.
Can two rollouts touch the same market at once?
Yes, but each apply writes on top of the market's current saved values in its own transaction, so whichever one commits last wins for any setting they both changed — check the market's Customized settings afterwards if you're running overlapping rollouts.
I tried to cancel a scheduled rollout but got an error.
That means it already applied in the background before your cancel reached the server — Lulu refuses rather than silently ignore it, and shows the rollout's real current status (Applied) instead.