Plan the launch like an album.Ship it like a machine.
In KMUPIM, a release is its own object. You plan, review, and ship it as one cohesive operation. No master spreadsheet, no last-minute bulk edit in Shopify.
Release as object
In KMUPIM, a release is not an Excel column or a Slack channel. It is its own database row with launch date, status, linked products, linked assets, approval state, and audit history.
Versioned
Product snapshots capture the full state before the drop. Fields, variant list, option schema, custom fields. Diffable and restorable. A release is therefore reproducible, not a one-shot.
Scheduled Publish
The product-release-schedule-tick job runs in the background and checks due releases. At the scheduled time, the product-release-publish job writes back to the Shopify metafields. The team sleeps.
Micro-releases
Not every drop is a season. A single variant correction, a photo refresh, an SEO update. Micro-releases use the same publish path, with logs, without overhead.
Five stages.No hidden states.
Every stage is visible. Every transition is logged. Who moved the release from Review to Scheduled and when is in the audit log. Even 18 months from now.
- 01DraftSelect products, set launch date
- 02In ProgressAssign assets per variant and image role
- 03ReviewReadiness rollup shows missing approvals
- 04ScheduledLocked. No double-publish possible
- 05PublishedWritten to Shopify, audit entry final
Who's blocking.What's blocking. Since when.
The release detail view shows per child product which variant still lacks an approved image role, which approver is silent, and which stock contract is not linked. No "let me ask around" — a list instead.
Eight details. All active.
- 01Per-asset gate bar on approval state
- 02Readiness rollup per child product
- 03Lock semantics prevent race conditions
- 04Unpublish and channel rollback as its own job
- 05Append-only audit log on every mutation
- 06Kanban view on product releases
- 07Custom records on the release object
- 08Custom fields from metafield mirror