A 3K WooCommerce store in a week, product data included

Ask an agency why they under-quote WooCommerce projects and you'll get the same answer: the store setup is predictable, but the product data is a swamp. Fifty products with variations, images, categories and prices — nobody budgets honestly for the data entry, so the “simple store” quietly eats its margin. Here's the 3K WooCommerce store done honestly in a week: the storefront, the payments, and — the part that changes the quote — the product catalog imported, normalized and reviewed instead of typed.

The 3K price point targets a specific client: the small brand or local business with a real but bounded catalog — 30 to 120 products — moving off Etsy, a social shop or an aging site. They don't need subscriptions, B2B pricing or ERP sync; they need a clean store that sells, delivered before their next season. That's a week, if the data entry isn't manual.

---

The 3K store, scoped honestly

• Storefront pages. Home, shop, category pages, product template, cart/checkout, plus the trust set: shipping, returns, contact.
• WooCommerce configured properly. Payments (card + one local method), shipping zones and rates, taxes, transactional emails branded.
• The catalog, imported. Up to ~120 products from the client's spreadsheet, feed or photo folder — variations, images, categories, SEO fields included.
• Launch checks. Test orders through every payment path, the pre-launch checklist, and a link crawl.
• Not included: product photography, copywriting from nothing, subscriptions/memberships, multi-currency, ERP integrations — all quotable extras.

Days 1–2: storefront and configuration

1. Tokens and templates first, as always: global styles, then the product template and category layout as native builder parts — “Build the product page: gallery left, buy box right, tabs for details/shipping, related products band.”
2. Store pages by brief: home with featured categories and bestsellers band; the trust pages from the client's policies, formatted and placed.
3. WooCommerce configuration through typed operations with approval: payment gateways, shipping zones (“NL flat €4.95, free over €75, pickup enabled”), tax settings verified against the client's registration.
4. Email pass: the order confirmation set to brand colors and a human tone — the most-read page of the whole store.

Days 3–5: the catalog — where the margin lives

This is the stage that used to be 20 hours of typing, and it's now a supervised import. The complete method is in bulk-create WooCommerce products from a spreadsheet — here's how it lands inside the week:

1. Take the client's data as it exists — the messy sheet, the export, the folder of photos with a price list. Don't make them clean it; that request stalls projects for weeks.
2. First batch, 10 products: map columns to fields, match images by SKU or name, review the plan (creates, updates, skips), approve, inspect the results in the storefront. This calibrates everything.
3. Then the rest in batches of 30–50: size/color columns become real variations on variable products; categories and attributes assigned; duplicates reconciled by SKU.
4. Copy pass: missing descriptions drafted on-brand from the product name and attributes — as drafts for the client's yes, never straight to the storefront.
5. SEO pass across the catalog: titles, metas and alt text patterned and applied in one sweep.
6. The corpus gate: spot-check 15 products end to end — price, variation, stock, image, category. One hour that prevents the launch-day refund.

Days 6–7: orders, checks, launch

1. Test orders through every path: card, the local method, free-shipping threshold, a variation product, a refund. Each leaves a paper trail.
2. Pre-launch checklist plus a link crawl — report saved for the handoff pack.
3. Launch, then the first-week watch: orders arriving, emails delivering, nothing 404ing.
4. Handoff call: the client learns orders and stock; the store's technical layer goes onto the care plan.

The ledger

• Hand-built equivalent: 35–50 hours — of which product data alone is 15–25, the part that always overruns.
• This pipeline: 12–16 hours — storefront and config are directed builds; the catalog is batch review instead of typing.
• At 3K: healthy margin on a one-week turnaround, plus the natural upsells — more products, seasonal landing pages (the 2K one-day page), and the care plan every store needs.

Store-specific failure modes

• Quoting before seeing the data — 40 clean rows and 400 chaotic ones are different projects. Look at the sheet before the number leaves your mouth.
• Importing everything in one heroic batch — the first 10 calibrate mapping; skipping that step multiplies every mapping error by the catalog size.
• Letting drafted product copy go live unreviewed — brand voice is the client's call; the draft gate exists for it.
• Skipping refund and local-payment test orders — the paths clients actually use are the ones agencies test least.

The store week checklist, printable

• Catalog data sighted before the quote — size, mess level, image situation.
• Contract clock starts at data delivery, and the client knows it.
• Tokens, product template and category layout before any product exists.
• Payments configured with the local method; taxes checked against the client's registration.
• Transactional emails branded — the order confirmation reads human.
• Calibration batch of 10 inspected in the storefront before the bulk runs.
• Variations from columns verified on the variable products separately.
• Drafted copy through the client's voice check before publish.
• 15-product spot-check: price, variant, stock, image, category.
• Test orders through every payment path including a refund; checklist; launch; first-week watch.

The trust layer: what makes a small store feel safe to buy from

Before the list, the principle: a visitor who has never heard of the brand is performing a risk calculation in about eight seconds, with the checkout as the stake. Every element below exists to lower the perceived cost of being wrong — which is why trust work outconverts another design polish pass at this tier, and why it's scheduled work in the week rather than leftovers.

Small stores lose checkouts to doubt, not to design — and the week has a half-day budgeted for the trust layer precisely because it converts. The concrete list: shipping and returns pages written in human sentences with real numbers (“orders before 15:00 ship same day; returns within 30 days, we pay the label above €50”), the contact page with a face and a real address, trust badges only where they're true (payment logos yes, invented “satisfaction guaranteed” seals no), and prices that include what they include stated plainly — VAT and shipping surprises at checkout are the top abandonment trigger in EU small commerce. Reviews come later honestly: launch with none rather than with obviously purchased ones, then let the post-purchase email (wired during the email pass) ask for them — ten real reviews in month one outperform fifty suspicious ones on day one. None of this is design work; all of it is why two visually identical stores convert differently. The checklist treats the trust pages as launch-blocking for that reason.

FAQ

What catalog size fits the 3K week?

Thirty to about 120 products comfortably, variations included. Past that, the storefront week holds but the catalog becomes its own line item — price data by the hundred, not by vibes.

Can it import from Etsy or a social shop?

Exports from those platforms are just sheets and image folders — exactly what the import pipeline eats. The mapping batch calibrates their quirks.

Does the client need WooCommerce experience?

No — the handoff covers orders, stock and refunds in their dashboard, and the transactional flows are pre-wired. The technical layer stays on the plan.

What about ongoing product updates?

Same pipeline, smaller batches: the client sends the new sheet, you run a reviewed update batch — updates by SKU, no duplicates. Many agencies fold a monthly batch into the care plan.

The store prompt set

• “Build the product page template: gallery left, buy box right with variation selectors, trust icons under the button, tabs for details/shipping/returns, related products band. Global styles.”
• “Configure shipping: NL flat 4.95, free over 75, BE/DE zone at 7.95, pickup enabled with address [x]. Show me the zone table before saving.”
• “Map this sheet's columns to product fields: [paste header row]. First batch of 10 only — I want to check the mapping before the rest.”
• “Size and Color columns become variations on variable products; price deltas per the sheet's modifier column. Show the plan for the 26 variable products separately.”
• “Draft descriptions for the 18 products missing them: two sentences, plain and warm, from name plus attributes. Drafts only.”
• “Meta pass across the catalog: title ‘[Product] — [Brand]’, description from the first sentence of each product's copy, alt text from product name plus variant.”
• “Place a test order for a variable product with the local payment method, then refund it. Report each step's result.”

A worked example: the ceramics studio

The 3K shape: a ceramics studio selling at markets and on Instagram DMs, moving to a real store before the holiday season. Their “catalog” is a photo folder and a price list in Notes — 67 products, a third with size variants. Day one sets a warm, minimal storefront on their earthy palette; day two wires iDEAL plus cards,市场-weight shipping zones, and the branded order email that replaces their DM confirmations.

The catalog days turn the folder into commerce: the calibration batch of 10 surfaces that their photo names encode glaze colors (“vase-lg-moss.jpg”), so image matching keys on that pattern for the rest. Variants build from the price list's size columns; 18 missing descriptions get warm two-line drafts the owner edits in an hour (“that's my voice, but I'd never say artisanal”) — which is exactly what the draft gate is for. The corpus check catches two price typos an order would have made expensive.

Test orders Thursday — including the refund path, because market sellers refund — and live Friday with 67 products, five days after the folder arrived. The studio's first weekend brings eleven orders; the owner's note says the branded order email got more compliments than the pots. Fourteen hands-on hours inside a 3K invoice, and a certain January conversation about a spring-collection batch already scheduled.

The seasonal reality: why the week matters

The 3K store client is almost always season-driven — holidays, wedding spring, festival summer. This changes the sales conversation: the quote isn't competing with other agencies, it's competing with the calendar. A four-week agency timeline misses the season and therefore isn't a higher-quality option; it's a zero. The one-week pipeline makes September conversations produce October stores — say that sentence in the pitch, because it's the one the client repeats to their partner. And schedule honestly in return: the week promise holds when the data arrives on day one, so the contract's clock starts at data delivery, not signature.

The store's plan: different drumbeat, same engine

• Stores rot faster than brochures: prices change, stock lies, payment providers deprecate things in emails nobody reads. The store tier of the care plan runs the same engine with commerce checks added.
• Monthly: the update pass treats WooCommerce and payment plugins as riskiest-last with a test order after; the crawl covers product pages the sitemap forgets.
• Quarterly: a catalog batch — new products in, retired ones properly hidden with redirects, seasonal collections rotated.
• The number: store plans start a tier up (700-ish) because the blast radius includes revenue directly — an argument clients accept the first time checkout breaks anywhere, for anyone.

What payment methods matter beyond cards?

The local ones — iDEAL in the Netherlands, Bancontact in Belgium, and their equivalents per market — often carrying half or more of checkout volume. A store launched card-only in those markets underperforms from day one and nobody knows why. The brief asks where customers are; the config follows.

How do we handle stock the client tracks elsewhere?

At this tier, simply: WooCommerce becomes the source of truth, and the handoff teaches the client stock adjustments. Real two-way sync with a POS or warehouse system is genuine integration work — quote it separately when the client's operation actually needs it, not preemptively.

The bottom line

The 3K store works because the swamp is drained: storefront by directed build, configuration by typed operations, and the catalog as reviewed batches instead of typing. Everything WooCommerce over MCP can do is on WooCommerce + MCP; the price-ladder context is 1K vs 5K vs 25K; the toolset is in the Bundle (pricing).