Bulk Catalogue Import
Drop a CSV whose first column is URLs. A background job runs Page-to-Campaign on up to 200 rows, streaming a live progress bar.
Runs out of credits mid-batch? The job pauses gracefully with a clear per-URL error log — no silent failures, no wasted work.
What Bulk Catalogue Import really does
Drop a CSV whose first column is URLs. A background job runs Page-to-Campaign on up to 200 rows, streaming a live progress bar.
The overview panel below is an AI-generated isometric infographic — every card is grounded in a real, shipped capability of this module. No mock-ups, no lorem ipsum.
- 1One workflow — not another tab to remember
- 2Zero setup — inherits your Brand DNA on day one
- 3Every AI output stamped with its DNA version for audit
- 4Consent, disclosure and rate-limits are on by default
A guided 4-step workflow
Every AI action in the Studio follows the same shape: fetch inputs, ground them against your brand, generate variants, then park them in Approvals.
The workflow infographic below is regenerated from this module's shipped capabilities so it always tells the truth about what runs end-to-end.
- 1Prepare — inputs come from your DNA, URLs, catalogue or ad-hoc briefs
- 2Configure — pick frameworks, tones, sizes and audiences
- 3Run — the LLM drafts; credits are checked before spend
- 4Approve — every draft becomes a pending row for a human to sign off
Speed, coverage and cost — measurable from day one
Teams typically see minutes-not-days turnarounds on campaign kits, dramatically wider coverage per week, and clean attribution back to the assets that actually converted.
The stat-card infographic below is a stylised, editorial visualisation of the outcomes this module unlocks — grounded in the capability list your customers actually see.
- 1Minutes, not days — a full campaign kit in one sitting
- 210× coverage — brief 10 products in the time it took to brief 1
- 3Lower cost-per-lead — locked variants + attribution beat guesswork
- 4Consistent brand — every asset uses the same DNA snapshot
Safe, consent-first, and human-approved
Prohibited claims and restricted words are blocked at generation time; PII is redacted before storage; every approval and rejection stamps an immutable audit row.
The trust panel below visualises the specific policies this module enforces — role scope, consent, rate limits and disclosure.
- 1Human-in-the-loop — nothing publishes without a tap
- 2Immutable audit trail on every generation and decision
- 3Prohibited claims + restricted words auto-flagged
- 4Credit guardrail — the LLM refuses to run when balance is out
