In this guide 6 sections
Have the vendor show, live, how a product holds its age grading and warnings, where test reports are kept and how a recalled lot reaches past buyers. Then ask how a subscriber moves up a size, how a registry works and how restricted ad words are caught. Judge by the demo, not the brochure.
Start with how a product carries its age grading
Have the vendor create a stroller listing with a weight limit, then a toy listing with a small parts warning, live and in front of you. A text box in the description is no field at all.
Look for separate fields for minimum age, maximum age, weight band, material and warning text. Try to publish a product with a required field left empty. A good system refuses. Then check where the warning appears: on the product page, on the invoice and in the feeds that go out to marketplaces and ad platforms.
Watch the page as a shopper would see it. The weight limit should sit near the price. The warning should sit near the button.
- Minimum and maximum age as numbers, not words in a title
- Weight limit and weight band fields
- Warning text that prints on the page, the invoice and the feed
- A rule that stops publishing when a field is empty
Ask where test reports live and who can change them
A report should attach to the product and to the supplier lot it covers, not float loose in a shared folder. Watch one being uploaded, replaced and searched for. Next, find out how the system reacts at expiry. A reminder beats a spreadsheet nobody opens.
Check permissions. Customer support may need to read a report to answer a worried parent, but only the compliance owner should be able to replace it. Look for a change history.
Time it. Pick any product and ask for its report. A marketplace will not wait.
Test a recalled lot before you sign
This question separates baby retail software from general shop software. Give the vendor a lot number, then watch whether the system lists every order that shipped it, with the buyer, the date and the courier. It should take a minute. A day of spreadsheet exports is a bad sign.
Then see what can be done with the result. You will want to hold the remaining stock, write to every affected buyer, offer a refund or a replacement and record who replied. Check whether the notice goes out from your own domain.
Ask for the log. A regulator or a marketplace may later want proof that each affected buyer was told, and when, and which of them answered.
- Search orders by supplier lot
- Hold the lot from sale in one step
- Notice to past buyers by email or text
- Refund or replacement tracked per order
- Log of who was told and when
Ask how size up subscriptions and registries behave
Watch a size swap on a diaper or formula plan. Cancelling and re-creating the plan is not a swap. Then check whether the system can prompt a parent to move up before the next shipment, using the baby’s birth date or a logged weight.
For a registry, look for a reserve option, group gifts on big items and a way to mark items bought elsewhere. Ask what a giver sees and what a parent sees. A registry that shows the parents’ street address is a problem.
Then see whether reserved items come off live stock. An add-on that cannot see the warehouse will sell the last pram twice, and the second buyer learns of it only at dispatch.
- Size swap inside an active plan
- Skip and pause without a phone call
- Registry reserve linked to live stock
- Group gift on one item with a shortfall rule
Ask about restricted words in listings and ads
Ad platforms and marketplaces limit some wording for children’s goods. Hypoallergenic, medically tested and safe for newborns all draw attention. The rules change often, so you need a word list you can edit, not one baked into the software.
Check whether titles, descriptions and ad feeds are scanned against your list before anything publishes, and whether a flagged word stops the product or only warns. A flag that waits for a person to approve is better than a silent failure after an ad is rejected.
Take these questions to every demo and write the answers on one sheet per vendor, so that nobody has to remember what the third salesperson promised. Make each run the stroller and the recalled lot live.
Baby and kids store vendor question sheet
The sheet fits on one page, in five blocks that match the sections above: product fields, test reports, recall, subscriptions with registries, and restricted words. Each row holds the question, a column marked shown live, described only or not offered, and a notes column. Keep one sheet per vendor. Total the live demonstrations at the bottom.
Open a blank worksheet to printQuestions owners ask
Is a general ecommerce platform enough for a baby store?
It can be, with care. Check whether age grading, warnings, lot level recalls and size up subscriptions are built in, added through apps or missing. The gaps decide how much extra work follows.
Should the platform store our test reports?
Prefer one that attaches reports to products and lots. If reports sit in a shared drive, make sure each product record links to the file and that a named person owns renewals.
How do we judge a recall feature?
Give the vendor a lot number and time the answer. A good system finds every order in one search, holds the remaining stock and drafts the notice to buyers before you ask.
Does a registry need a separate app?
Not always. Some platforms include one. Others rely on an add-on that may not see stock. Ask to see a registry item reserve against live stock.