One record
Content lives on the product — so the page never drifts from the catalog.
In most setups a product’s description lives in one system and the product — its name, price, and stock — in another, linked by hand; change the product and the words quietly fall behind. In oozmi the description lives on the product itself, right next to the price and the stock, along with its drafts, translations, and history. There’s nothing to keep in sync, because there’s only ever one copy.
What that unlocks
Four things you can do once the words live on the product.
Because the words live on the product, the place you write in is also the place you test, target, and extend. Four everyday jobs that normally mean a separate tool — or a ticket to engineering — happen right here instead.
- 01 Build or change anything Edit any block, page, or blog post in a visual Builder — or just ask. The SEO module keeps it on best practice.
- 02 Write email & SMS the same way Start from a template, build it, or describe it to the assistant. Personalized from the same customer record.
- 03 Test it, and target by segment A/B test your storefront, email, and SMS — and show each customer group its own version.
- 04 Add a whole new range Spin up a new product category with its own data and pages. Search and recommendations pick it up on their own.
Email & SMS
Email and SMS are built the same way.
Pick a template, lay it out in the Builder, or just describe it — “a back-in-stock note for members.” The assistant writes the email, drops in the product and the member price, and does the same for the SMS. Because it’s reading the customer record, every message already knows who it’s going to.
- Start from a template — or a blank canvas in the Builder.
- Or write it with AI — in plain language, for email or SMS.
- Personalized from the record — the right product, the right price, the right name.
One place to write it — and it already knows the customer, the product, and the price.
Test & target
Show each kind of customer its own version — and test which one wins.
Pick a group of customers — the same segments you already keep in your CRM — and give them their own storefront, email, or SMS. Not sure which version lands? Run both as an A/B test and let the numbers decide. The winner can roll out on its own.
- A/B test anything — storefront, email, and SMS.
- A version per segment — members see one thing, first-time visitors another.
- Straight from the CRM — no second list to keep lined up.
One segment, every channel — and proof of which version works.
- A Free-delivery banner 3.1%
- B Member-price hero 4.6%
Extend the model
Add a whole new kind of product — pages, search, and all.
Selling something you’ve never sold before? Define the new category once — its own details, its own page — and the rest of the platform notices. A category page is built from your template, recommendations start learning it, and search understands it by meaning. No migration, and no separate “add it to search” project.
- DetailsOrigin, caffeine, format
- PageFrom template
- Languages
- A category page Built from your template — live on the store, in both languages.
- Recommendations Start suggesting Tea wherever it fits — no retraining project.
- Search Finds it by meaning — “something calming” turns up Tea.
One change
Change it once. It updates everywhere.
Whether it’s a product description, a storefront block, or a page, there’s no separate “publish and send it out to the other systems” step. You ask, the assistant changes it, you approve — and everywhere those words appear is already showing the new version.
-
The assistant makes the change
Ask in plain language — it rewrites the copy, right on the product.
No separate content tool, no copy to track down. The assistant edits the product itself and leaves you a draft.
-
You approve it
See the new wording next to the old.
Approve it or send it back. Nothing goes live until you say so.
-
It’s saved
Approving it is the whole publishing step.
No waiting for the site to rebuild, and no copy pushed off to another system.
-
Your store shows it
The product page already has the new words.
There was never a separate copy to refresh, so nothing lags behind.
-
So does everything else
Search, your email campaigns, and the assistant.
Everything reads the same product, so nothing falls out of step.
Every change stays attached to the product — so anyone can see what it said last week and who changed it, without leaving the page.
Bring one thing you wish you could change without a developer.
We’ll build it live — in the Builder and by chat — run it past the SEO check, show a version to one kind of customer, and prove the change lands everywhere at once: your store, your search, your campaigns. If it holds up against your real store, we talk pilot.