Why batches
Publishing prices one record at a time offers no review step and no way to make a set of changes go live at the same moment. A batch solves both: it collects the records, requires an approval before anything publishes, and carries a single effective date so every price in it takes effect together. Most price creation flows put records into a batch automatically. Mass-create and bulk-set operations find or create an open batch keyed on the effective date, so changes sharing a date coalesce into one batch. You can also create a batch explicitly and add records to it.The review lifecycle
A batch moves through a fixed set of states. You cannot approve a draft directly — it must first be submitted for review, mirroring a two-person workflow where the author submits and a separate reviewer approves.| Status | What it means |
|---|---|
draft | Being assembled. Freely editable; add or remove records. |
pending_approval | Submitted for review. Awaiting a reviewer. |
approved | Approved and scheduled to publish on its effective date. |
cancelled | Withdrawn before publishing. |
Assemble a draft
Create the batch (or let mass-create make one for you) and add price records.
Set a name and the effective date the prices should go live.
Submit for review
Move the draft to
pending_approval. MerchantOps records who submitted it
and when.Approve or reject
A reviewer with approval permission approves the batch (moving it to
approved) or rejects it. Approval requires the batch to be in
pending_approval — not draft.Rejecting a batch discards its draft prices. Cancelling withdraws a batch that
has not started publishing. A batch that is already publishing or has published
cannot be cancelled or deleted.
Required effective date
Every batch carries an effective date, entered as a calendar date and interpreted as local midnight in your organization’s publishing time zone. This date is both the schedule (when the prices go live) and the grouping key that auto-batching uses to coalesce same-day changes.What you can edit, and when
Edit rules tighten as a batch advances, so a reviewer can trust that an approved batch will not silently change:| Status | Editable |
|---|---|
draft | Name, description, effective date, assignee, publishing target, notes. |
pending_approval | Effective date and notes only. |
approved | Locked. |
Scheduled publishing
An approved batch publishes on its own when its effective date arrives — you do not have to trigger it. You can watch progress on the batch’s publish-status view, which reports how many prices have published, failed, or been skipped, broken down by publishing target. If you need a batch to go out immediately — for testing or an emergency reprice — a Publish Now action lets an approver publish an approved batch without waiting for the effective date. Publish Now is not available for a batch whose effective date is in the future; create a batch dated for today instead. Where prices are published (the connector, target, and environment) is covered in the Publishing section.Publishing overview
How batches are delivered to external systems.
Comparison & proposals
Generate batches from reviewed price-change proposals.