How product launches work
A launch is a checklist for one product's go-live. It has a target date, an owner, its launch channels and notes. A product has at most one open launch at a time. A launch doesn't change how SKU.io plans, buys or sells the product. That stays with the product's lifecycle state.
The checklist
When you start a launch, it copies the launch checklist from your settings. Later changes to that checklist apply to new launches only, so a checklist in progress never changes under you.
Each item has an owner, a due date and a status:
- Owner: the item's default owner from the checklist, or else the launch owner.
- Due date: the target date less the item's Due (days before launch). If you change the target date, every due date you haven't set by hand moves with it.
- Status: To do, In progress, Blocked, Not needed or Done.
You can also add your own items to one launch. They show a Custom chip.
Automatic checks
Every checklist item has a check. An item checked by a person waits for you. The others look at your data and show what they found in the Evidence column:
| Check | Passes when | Evidence, for example |
|---|---|---|
| Stock on hand or an inbound purchase order | The product has stock on hand, or units on an open purchase order | 1,200 on hand, or PO-1043: 5,000 inbound with the expected date |
| A document of a chosen type is on file | A document of one of the item's types is on the product or on one of its lots | The document type and file name |
| Listing live on each launch channel | The product has a live listing on that channel. The launch gets one of these items for each launch channel | No listing on Walmart yet |
| Product has enough images | The product has at least the item's number of images | 2 of 3 images |
A document check can also pass on images alone when its item sets Or at least N images. The default Marketing assets ready item works this way.
When a check passes, its item becomes Done and shows Checked automatically. If that check stops passing later, for example because the stock sold out, the item goes back to To do. An item that you marked done yourself stays done.
You can mark an automatic item done before its check passes. SKU.io then asks why, and shows your reason on the item, such as Marked done by Jane: COA held by the co-packer, copy on email.
Sometimes a check can't run. The item then says why, with a link to the fix:
- Choose the channels this product launches on: the launch has no channels yet.
- This sales channel is no longer connected: reconnect it under Apps & Integrations.
- No document types are set for this check: set them in the launch checklist.
- Products can't hold … documents yet: the check can find these documents on the product's lots only.
Checks run when you start a launch, when you open it (if they last ran more than 10 minutes ago), when you click Re-check now, and every night for every open launch.
Launch status
| Status | When |
|---|---|
| Planning | A new launch, before any item is started |
| In progress | At least one item is in progress or done |
| Ready | Every item is done or not needed. If an item reopens, the launch goes back to In progress |
| Launched | You clicked Mark launched |
| Cancelled | You clicked Cancel launch |
SKU.io moves a launch between Planning, In progress and Ready for you. You set Launched and Cancelled yourself. Both make the checklist read-only. Reopen puts the launch back under automatic status.
Alerts
A launch can raise two alerts. They go to users who can edit products, and to admins:
- Product Launch: Checklist Items Overdue lists each overdue item with its owner. It clears itself once nothing is overdue, or once the launch is launched or cancelled.
- Product Launch: Ready to Launch is sent once, when every item is done or not needed. It's sent again only if you reopen the launch and it becomes ready again.
SKU.io checks for both every night. To choose how you receive them, see Set your own alert notifications.