I’m building a family of tools for the details behind a store: product facts, product pages, landing pages, and email. Each takes a defined input and leaves you with something to use.
Start with the problem in front of you. You do not need all five.
Repair a product family against its supplier sources.
$299USD / once
Bring
One Shopify-style catalog CSV, up to 25 SKUs, and up to five readable supplier files with exact-item evidence.
Take away
A reviewed full catalog snapshot, before-and-after ledger, supporting evidence, import instructions, and up to ten post-import CSV rechecks.
The useful boundary
Selected existing titles, scalar product metafields, weight in grams, and variant image URLs. Customer decisions resolve conflicts. No store access or automatic import; review the full snapshot against a fresh export before use.
Standalone prices checked October 11, 2026. The destination confirms current eligibility, availability, and final price. This page does not take payment or transfer project files.
Put the work in order
What needs to be true first?
Facts before presentation.
If the specification belongs to the wrong SKU, start with the source and identity. Specstead’s worked examples cover variant identity, source conflicts, and the import handoff. A polished page cannot settle an unresolved fact.
Review before implementation.
Page Heckler supplies a diagnosis and copy brief. Pagework prepares files for a supported Dawn section. The review may be enough on its own; a separate implementation purchase is optional.
Existing email or a new one?
As Offered works on supported existing percentage-off HTML campaigns. Fold starts a new email. Choose according to the starting material, not the similarity of the names.
For an agent helping a merchant
Find the scope. Keep the decision.
The structured directory and reading copy use the same records as this page. They describe jobs and destinations; they do not authorize access or payment.
Identify the exact task, the customer’s inputs, and the intended output.
Obtain authorization before sending customer files. Keep private workspace links, capabilities, recovery codes, and source contents out of referrals.
Present unresolved decisions and the reviewed scope to the merchant. The merchant completes payment and controls any import, installation, or send.
For a local check before using a paid service, the Commerce Evidence Toolkit compares supplied product records, feed snapshots, and dimensions. The product-data contract explains which facts and unknowns to retain.