FAQ
These answers focus on how PrepackFlow Atlas behaves for apparel and footwear pack ordering across guided setup, storefront runtime, and checkout validation.
- Reusable packs stay DB-first and easy to review.
- The main admin journey now favors Quick Start, Products, Pack Library, and Review & Publish.
- Cart display is grouped for readability while fulfillment remains variant-based.
Why does the admin start with Quick Start now?
Quick Start is the first-run workspace for operators who want to launch wholesale pack ordering quickly without opening technical tools first.
It shows setup progress, recommended next steps, unresolved blockers, and publish readiness so a team can follow a single guided path.
- Setup progress and next actions
- Publish blockers in merchant language
How do Products and Pack Library work together?
Products is where operators prepare specific SKUs for pack ordering and see whether a product still needs sizes, a pack, or extra attention.
Pack Library stores reusable size runs such as Pack A, Pack B, or Full Run so the same wholesale structure can be applied across multiple products.
- Product-level readiness control
- Reusable pack cards across apparel and footwear lines
What do buyers see on the storefront?
Buyers see visual pack cards that explain included sizes, MOQ, order step, and availability in plain wholesale language.
After a pack is added, the cart shows a grouped pack summary so the order is still easy to read even though fulfillment remains variant-based behind the scenes.
- Buyer-facing pack cards
- Grouped pack summaries in cart
What do cart transform and validation enforce?
Cart transform keeps the cart readable by grouping pack-oriented display for lines that were added as one pack action from the storefront.
Validation stops naked component lines, stale runtime versions, wrong pack ratios, increment violations, minimum-order rules, and customer-segment restrictions.
- Readable grouped cart display
- Final checkout guardrails
Where did imports, templates, logs, and simulator go?
Those tools still exist, but they now live under Advanced so the core operator journey stays simpler.
Expert users can still reach templates, CSV import, logs, simulator, and other technical surfaces without disrupting the main setup flow.
- Advanced stays available
- Main journey stays simplified
How do I ask for help or request a feature?
Use the public feedback page for roadmap ideas, documentation corrections, or general support notes. Messages are stored in the operator inbox for review.
- Anonymous submission supported
- Optional email for follow-up
Still comparing options?
The product docs show the guided admin journey and the buyer-facing runtime flow used for shared pack ordering.