Merchant FAQ

FAQ

These answers focus on how PrepackFlow Atlas behaves for guided pack ordering across setup, storefront pack display, and checkout validation.

Generated FAQ illustration showing question bubbles around a support conversation.
Merchant FAQ The FAQ answers common setup, billing, storefront, and validation questions in merchant language.
Key points
  • Reusable packs stay easy to review before they are published.
  • The main admin journey now favors Quick Start, Catalog Items, 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 starts with Shopify product search, recommends the best starter pack, keeps extra templates collapsed, and then guides size mapping, buyer previews, blockers, and publish readiness in one path.

  • Setup progress and next actions
  • Publish blockers in merchant language

How do plan changes work?

PrepackFlow Atlas uses Shopify managed pricing for the public listing, so merchants choose, upgrade, or downgrade from Shopify's hosted plan selector instead of contacting support.

The Plan & Billing tab shows the current saved plan state and links back to Shopify when paid publishing access still needs approval.

  • Plan changes stay inside Shopify
  • Paid publishing unlocks after Shopify plan approval

How do Catalog Items and Pack Library work together?

Catalog Items 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 and case packs so the same wholesale structure can be applied across multiple products.

  • Product-level readiness control
  • Reusable pack cards across product 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 grouping and validation enforce?

Cart grouping keeps the order readable by showing one pack summary for lines that were added as one pack action from the storefront.

Validation stops direct size-line ordering, outdated published setups, 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
Next step

Still comparing options?

The product docs show the guided admin journey and the buyer-facing storefront flow used for shared pack ordering.

Open docs