The Content Collection System Behind a Two-Week WooCommerce Rebuild

A two-week delivery target on a WooCommerce rebuild is achievable. What breaks it is almost never the development. It is the fortnight lost waiting for the client to send product details, photos, prices, and policy copy. On a recent rebuild for a specialist retailer, the fix was to remove the blank page: the client never started from nothing.

Pre-fill from the client’s own live site

Before asking the client for anything, their existing website was pulled into a structured product database: every product they already sold, with its current name, description, and image imported as a starting point. The client’s job changed from "write all of this" to "check this, correct the price, fill the three gaps". That is a fundamentally easier task, and a faster one.

One board, clear ownership

The collection workspace is a set of linked databases: a product collection, a supplier directory, a research queue for items the developer sources independently, and a content library for logos, images, and documents. Every row has a status and an owner, so at any moment it is obvious what is done, what is with the client, and what is with the developer.

A client upload dashboard

Instead of email threads with attachments, the client has a single view showing progress at a glance: categories complete, categories outstanding, and exactly what each outstanding one needs. It turns "where are we with content" from a meeting into a link.

Decisions get logged where they happen

When a phone number changes, or a product line is dropped, or a category is renamed, it goes into a decision log with a date. Weeks later, when someone asks why the old number is gone, the answer is recorded. Undocumented content decisions are where scope quietly expands.

What this changes about the timeline

• The client is never blocked by a blank form, so content comes back in days, not weeks.
• The developer is never blocked waiting to know what is missing, because the dashboard shows it.
• Go-live gating is honest: the build finishing on schedule and the content being complete are tracked separately, so it is clear which one the launch is waiting on.

The build was delivered to staging on schedule. Where a project like this stalls is upstream of the code, and that is the part worth systematising.

Related