Muse for E-Commerce Sellers: Listing Drafts, Review Triage, and Restock Tracking That Matches Your Stock
An e-commerce seller setup for Muse: listing drafts built only from your spec sheet, a review and Q&A queue sorted by what needs a human, and a restock board driven by reorder points, with promos checked against stock before they are announced.

Selling online fails in small, ordinary places. A listing goes up with a dimension copied from the wrong variant. A question about sizing sits unanswered for four days while the shopper buys elsewhere. A promotion lands on a product with eleven units left, and the store sells out on the first morning and pays to advertise an empty page. Muse does the drafting and the sorting for those jobs, and you keep the publishing, the replies, and the orders.
This setup runs three jobs. Muse drafts listings only from the product facts you paste in, sorts reviews and product questions into a queue with draft replies you approve, and keeps a restock board built on reorder points rather than shelf counts. A promotion gets planned only after that board says the stock can carry it.
A good product description answers three things in plain language: what the product is, who it is for, and what it does for that person. Write to a specific customer, lead with benefits and give evidence for them, replace generic claims with specifics, and put the hard facts where a shopper can scan them. Put dimensions, materials, functions, and care instructions in the listing itself. Restock math needs the same specifics. A reorder point is average daily sales multiplied by supplier lead time in days, plus safety stock, and safety stock is the buffer for a busy week or a late delivery. A raw unit count tells you none of that.
The short version
- Draft listings only from a spec sheet. Every claim in the draft has to trace to a fact you pasted in, and anything missing is written as not recorded.
- Sort reviews and questions before you answer them. Product defects, safety issues, and angry customers go to a human first. Sizing, shipping, and care questions get drafts a human approves and sends.
- Reorder on a point: average daily sales times lead time, plus safety stock. Compare it against stock on hand plus stock already on order, minus stock committed to unshipped orders.
- Plan a promotion only against the restock board. If the featured product cannot carry the expected demand at full stock, change the offer, bundle it, or move the date.
- The failure mode to watch for is a confident listing with one invented detail in it, and the fix is a standing rule that Muse works only from the material pasted in that run.
The Setup: The Storefront Ledger
Call the whole arrangement the Storefront Ledger. The example I run it against is a seller with a 48-SKU home and kitchen store, selling through her own storefront and one marketplace, with two part-time helpers packing orders four days a week. Her inputs are ordinary: a spec sheet per product with dimensions, materials, variants, and care notes, the reviews and product questions each platform collects, a sales export covering the last 90 days, supplier lead times written down from the last few orders, and a short list of the promotion dates she cares about, which for her store is a spring refresh, a midsummer bundle, and the November gift season.
The ledger depends on a few standing pieces. A standing instruction from our memory guide holds the durable parts: the store’s voice for listings and replies, the product fields every draft must carry, the rule that Muse never states a dimension, a material, or a delivery time that is not in the pasted material, and the list of issues that always go straight to a human. Each request follows the same discipline as a task brief written for an agent: what product or queue is in scope, what the sources are, and what a finished draft looks like. The weekly restock check runs as a scheduled routine, so Monday starts with the reorder list already sorted.
The ledger borrows its queue discipline from the customer support lesson, where a human sends every draft and anything sensitive leaves the queue entirely, and its numbers discipline from the spreadsheets lesson, where a summary has to match the rows underneath it. Promo planning borrows from the marketers lesson: a campaign calendar is a working document with an owner and a stock check. Sellers who take checkout through Muse itself can also read how Shop Pay checkout works for Muse shoppers, because a listing that an agent reads needs the same clean facts a human shopper needs.
| Board | What it tracks | What decides the action |
|---|---|---|
| Listing board | Spec sheet, draft status, missing fields by SKU | Whether every claim traces to the spec sheet |
| Review and Q&A queue | Star rating, issue type, order link, draft reply | Issue type first, age of the item second |
| Restock board | Daily sales, lead time, safety stock, reorder point, stock on order | Stock position against the reorder point |
| Promo calendar | Date, featured SKUs, offer, margin floor | Stock cover for the featured SKUs |
Prompt 1: Draft the Listing From the Spec Sheet Only
Run this when a product is added, when a variant changes, and when a listing has collected enough questions to show where shoppers get stuck. Write one listing at a time. A batch run across ten products hides the one wrong dimension in a pile of correct ones.
Aim for the shape in Shopify’s guide to writing product descriptions: speak to the ideal customer, lead with benefits backed by evidence, avoid generic statements, and make the page scannable with bullets and white space. After a listing changes, watch conversion rate, return rate, and support inquiries. Those last two are your error detectors. A listing that raises conversion and raises returns by the same amount has usually promised something the product does not do.
Draft a product listing from the spec sheet below. Return: (1) Title: the product name, the main use, and the variant facts a shopper needs to pick the right one, using only the spec sheet below. (2) Opening paragraph: what the product is, who it is for, and the main benefit, with the evidence for that benefit taken from the spec sheet. (3) Bullets: the features from the spec sheet, each paired with what it does for the buyer, followed by a specs block with dimensions, materials, weight, compatibility, and care instructions exactly as written below. (4) Missing: every field a shopper would expect that the spec sheet does not give, written as not recorded. Rules: use only the material below. Do not copy wording from a supplier or manufacturer description if one is pasted in, rewrite it in our store voice. Do not state a size, a material, a capacity, or a delivery time that is not in the material below. Do not use a superlative unless the material below contains the evidence for it.
Spec sheet for this product, with variants: [paste it]. Store voice notes and words we do not use: [paste them]. Questions shoppers have asked about this product, if any: [paste them].
Read the Missing list before you read the draft. That list is the work order: fill each gap from the physical product or the supplier paperwork, then rerun. Publish only when Missing is empty or when every item left on it is a field your store has decided not to publish. Keep the spec sheet after the listing goes live, because the first sizing question that arrives is a test of whether the sheet or the listing drifted.
Prompt 2: Sort the Review and Q&A Queue, Then Draft Replies
Run this daily if your store takes more than a handful of reviews and questions a day, and twice a week below that. Sort before you draft. A defect report buried under twelve five-star reviews is the most expensive item in the queue, and it is the one a simple newest-first order hides.
For a small store, follow the practice in Bazaarvoice’s guide to responding to negative reviews: reply within 24 to 48 hours, use the customer’s name, restate the specific problem, keep the reply short, move order details into a private channel, and watch for the same complaint repeating across reviews. Repeated complaints point to a product or listing problem. Route them to the listing board or the supplier, with the review text attached.
Sort the reviews and product questions below, then draft replies. Return: (1) Human first: every item reporting a defect, damage, a safety concern, a missing order, or a refund request, plus every review of two stars or fewer, each with the issue in one line and the order reference exactly as written below. (2) Draft replies: for each remaining item, a reply in our store voice that uses the customer’s name as written below, restates their specific point, answers only from the product facts and policies below, and invites them to contact the store directly when order details are needed. Keep each reply under 80 words. (3) Repeats: any complaint or question that appears in three or more items below, listed once with the count and the items it came from. (4) Listing fixes: questions below that the current listing text below should already answer, each with the sentence you would add and where it belongs. Rules: use only the material below. Do not promise a refund, a replacement, or a delivery date that the policies below do not state. Do not invent a product fact to answer a question, write needs checking instead. Do not draft a reply to a safety concern, list it under Human first only.
Reviews and product questions, with names, dates, star ratings, and order references: [paste them]. Product facts and current listing text for the products named: [paste them]. Store policies on shipping, returns, and replacements: [paste them]. Store voice notes: [paste them].
Send replies only after you have read them against the policies you pasted in. The draft is allowed to be warm, it is not allowed to be generous with money or dates the policy does not cover. Work the Human first list yourself, in the same sitting, while the order details are still in front of you. A fast, specific reply to a bad review does more for the next shopper reading it than any reply to a good one, so give the hard queue your first attention.
Prompt 3: Build the Restock Board and Check the Promo Against It
Run the restock board weekly, and rerun it before any promotion is announced. Shopify’s min-max inventory guide gives the arithmetic: the reorder point is average daily sales times lead time in days, plus safety stock, and safety stock is maximum daily sales times maximum lead time, minus average daily sales times average lead time. Compare that point against your stock position, which is stock on hand plus stock already on order, minus stock committed to orders not yet shipped. Comparing it against the shelf count alone double-orders products that are already on a truck.
Promo planning works backwards from the date. In this setup the rule is six weeks out to choose the featured products and place any stock order the promotion will need, three weeks out to write the listing changes and the announcement, and one week out to test the offer at checkout and confirm the stock is physically in the building. Set the margin floor for the offer before anyone writes the announcement copy, and leave stretches of the calendar at full price, or the regular price stops meaning anything.
Build the restock board from the sales and stock data below, then check the planned promotion against it. Return: (1) Board: one row per SKU with average daily sales, lead time in days, safety stock, reorder point, stock on hand, stock on order, stock committed, and stock position, calculated only from the data below, showing the arithmetic for each reorder point. (2) Order now: every SKU whose stock position is at or below its reorder point, with a suggested order quantity that brings stock position back to the maximum level stated below, or written as no maximum recorded. (3) Watch: every SKU that will reach its reorder point within 14 days at its average daily sales rate below. (4) Promo check: for the planned promotion below, each featured SKU with its stock cover in days at the promoted sales rate stated below, flagged as can carry it, tight, or cannot carry it, with the reason. (5) Data problems: SKUs with no lead time recorded, sales data shorter than 30 days, or stock counts that disagree between the sources below. Rules: use only the material below. Do not estimate a lead time or a sales rate that is not in the data. Do not recommend an order quantity for a SKU listed under Data problems. If a promoted sales rate is not stated below, write promo rate not recorded and check cover at the average rate instead.
Sales by SKU for the last 90 days, or the period stated: [paste them]. Stock on hand, stock on order with expected dates, and stock committed to unshipped orders: [paste them]. Supplier lead times, average and maximum, with minimum order quantities and maximum stock levels: [paste them]. Planned promotion: date, featured SKUs, offer, margin floor, and expected promoted sales rate: [paste it].
Read the Data problems list first, then the Order now list, then the promo flags. A promotion flagged cannot carry it has three honest fixes: order earlier and move the date, feature a product with cover, or shrink the offer to a bundle that moves the overstocked line instead. Announcing first and hoping the supplier ships early is the fourth option, and it is the one that produces the apology email. Place the orders the board calls for yourself, in your supplier accounts. Muse prepares the list, a human commits the money.
What Can Go Wrong
The common failure is a listing that reads well and contains one fact nobody checked. It happens in a predictable way: the spec sheet is thin, the supplier page is open in another tab, and a dimension, a material, or a compatibility claim from that page, or from a similar product, ends up in the draft as if it were yours. The shopper finds the error before you do, usually after delivery, and the return, the refund, and the one-star review all cite the sentence you never verified. The same looseness in the restock run produces a quieter version of the failure, a reorder point calculated from a sales export that included a promotion week, which orders a season’s worth of stock for a normal month.
The fix is an evidence rule you keep in the standing instruction: Muse may state a product fact, a stock figure, or a date only when it appears in the material pasted in that run, and it writes not recorded or needs checking everywhere else. Then read the short lists first each run, Missing on the listing draft, Data problems on the restock board, and Repeats in the review queue. Those three lists are where this setup tells the truth about itself. If a SKU stays under Data problems for two weekly runs, treat filling that gap, a counted shelf, a lead time taken from real orders, as the task for the week, ahead of any new listing or promotion.


