Fishing tackle, UK and worldwideMagento 2 and Hyvä
Total Fishing Tackle
Hyvä frontend and integrations for a fishing tackle store with a deep catalogue: 11,482 products in the Carp category alone, read on 31st October 2026.
AI product content for Magento and Shopify catalogues.
Descriptions, attributes, alt text and translations from your own data, each item read by a person before import.
Product descriptions, attributes, alt text, meta descriptions and translations generated from the data you already hold, checked by a person against that data, and loaded into Magento, Adobe Commerce, Hyvä or Shopify by import. For merchants with hundreds or thousands of thin product pages. Estimated in writing once we have read the catalogue.
Is your catalogue like this?
What merchants say about their product pages.
-
Half our products still have the supplier's one-line description.
What it usually meansThin pages give buyers and search engines little to go on. Your own data usually says more than the page does.
-
Our filters do not work because sizes are written five different ways.
What it usually meansAttributes need normalising before filters, search and feeds can use them. That is often the bigger win.
-
We tried an AI plug-in and it invented features our products do not have.
What it usually meansIt was writing from a template, not from your data, and nobody read the output. Both have to change.
What you get, and what you do not.
Six things about every batch, the last of them a limit we keep on purpose.
Written from your data
Attributes, supplier sheets, specifications and images. No invented claims or measurements.
Every item read by a person
Each piece checked against the source data before import. Unsupported claims are cut.
Attributes, not only prose
Missing values filled and normalised so filters, search and feeds work.
Alt text and meta in the same pass
Every image described and every page given a meta description.
Translations per store view
From the reviewed English, reviewed again, with brand terms and units fixed in the brief.
What it is not
Not a button that writes pages on demand. If a product has no data worth writing about, we say so.
The same store, with and without us.
Without us
- Supplier one-liners on half the catalogue
- Filters broken by inconsistent attributes
- Images with no alt text
- Plug-in copy with claims nobody checked
- Store views left untranslated
- Content locked inside a tool
With Refined Commerce
- Descriptions written from your own product data
- Attributes filled and normalised to one format
- Alt text and meta descriptions in the same pass
- Every item read against the source before import
- Translations reviewed for each store view
- Import files you keep, and the old content kept to roll back
How we work through a catalogue.
Small first, then the whole catalogue in batches, each one read before it is loaded.
-
Step 1: A free first look
Send us the store address and an export of a few products. A senior person reads them and replies in writing.
Within two working days- Access we need
- None beyond a sample export, if you want to send one.
- What you receive
- A written view of what is thin, what data exists and a price for a sample batch.
-
Step 2: We read the catalogue and agree a brief
An export shows which products are thin and what sources exist. We agree tone, length, structure and what must never be said.
Within two working days of the export- Access we need
- A product export, and supplier data if you have it.
- What you receive
- A written brief and an estimate.
-
Step 3: A sample batch, reviewed with you
A small set generated, read by a person and shown to you. The brief is revised until you are happy with the voice.
First week- What you receive
- The sample, on a staging copy of the store.
-
Step 4: The catalogue, in batches
Each batch generated, read against the source data, corrected and imported to staging for you to see on the page.
Per batch- Access we need
- Import access to a staging copy.
-
Step 5: Import to live, with a way back
Loaded once you are happy with it, with the previous content kept so any item can be put back.
When you are happy with it- What you receive
- The import files, yours to keep.
What goes in, what comes out, and who reads it in between.
The model only ever sees what you already know about the product. The reviewer sees both.
What goes in
- Your attribute set and the values already filled
- Supplier spreadsheets and specification sheets
- Existing descriptions, including the good ones
- Product images
- The brief: tone, length, structure, what must never be said
Who reads it
- A person, reading each item against the source data
- Unsupported claims cut, not softened
- Products with too little data flagged back to you
- Terms, units and brand names checked against the brief
What comes out
- Descriptions, short and long
- Attribute values, filled and normalised
- Alt text for every image
- Meta descriptions
- Translations per store view
- Import files you keep
We price the work, not the clock.
- This service
- Priced as a project: a written estimate once we have examined the store.
- How you pay
- Usually spread across the length of the project.
- Our rate
- £80 an hour plus VAT, the same for every merchant.
- Never charged
- Account management, or the first look at your store.
Estimated in writing, with the review counted in.
The brief, the generation set-up, a person's review of every item and the imports are all included in the estimate. The cost scales with the number of products and the review each needs, so we put an estimate in writing after reading the catalogue rather than quoting a per-product price we would have to guess.
- Estimated in writing after we have read the catalogue
- Every item reviewed by a person before import
- Previous content kept, so any item can be rolled back
What happens first
How our pricing works - We read your export and count thin pages, missing attributes and images without alt text.
- Your best existing pages are read for the tone the brief should keep.
- You get the first draft of the brief, and the products we would start with.
The team behind this work.
A large catalogue built by this team. The figures are the store's own, measured by Google; they are not a claim about AI content.
Is this the right service for your store?
This is for you if
- You have hundreds or thousands of products with thin or inconsistent content
- You hold attribute, supplier or specification data the pages do not use
- You sell in more than one language
- You want a person to read every item
If your situation is different
- Only a few dozen products? A copywriter may be the better answer; ask us and we will say so.
- Product data missing or scattered? We can help you gather it first: see development.
- Want the pages found by AI shopping agents too? See ready for agent shopping.
Why merchants bring this work to us.
About Refined Commerce- 100%
Read by a person before it reaches your store
Every line of code and every piece of content that AI tooling drafts is read, tested and signed off by a senior engineer.
- 2008
Judgement that the tooling does not have
Years of Magento and Shopify work tell us what is safe to change on a trading store, and what needs a second look.
- 1
Point of contact, whoever does the work
Whether we do it for you or your own team does it with AI, the same senior person stays answerable for the store.
Questions merchants ask about this.
Will Google penalise AI-written product content?
Google's published guidance is that its systems reward original, high-quality content however it is produced, and act against content made to manipulate rankings. Content written from accurate product data, reviewed by a person and useful to a buyer is what that guidance asks for. We do not claim a ranking outcome either way.
Will it sound like every other store's AI copy?
Not if the brief is yours. The tone comes from your best existing pages, the structure is one you choose, and the facts come from your own data. The sample batch exists so you can say no to the voice before the catalogue is written in it.
What about products with almost no data?
We tell you. A product with a name, a price and one photograph gets a short, accurate description or none at all; nothing is invented to fill the gap. The catalogue read at the start lists these products so you can decide whether to find more data or leave them.
Can it fill in attributes as well as descriptions?
Yes, and for most stores the attributes matter more. Missing sizes, materials, colours, dimensions and compatibility values are filled from source data where it exists, normalised to one format and reviewed, so your filters, search and shopping feeds work properly.
Which platforms does this work on?
Magento Open Source, Adobe Commerce and Mage-OS, including Hyvä stores, through Magento's import or its API; Shopify and Shopify Plus through CSV import or the Admin API. The content is the same either way; only the loading differs.
Do we own the content?
Yes. It is loaded into your store, and you are given the import files too, so it is yours to keep, edit or move to another platform.
See where the store stands before the catalogue work starts.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
- Magento Open Source, Adobe Commerce and Mage-OS stores
- No login, no access, no obligation
- Written by a person, not a scanner
Free store health checkOne page, by email
Example report Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
- Platform
- Magento Open Source 2.4.4-p3
- Adobe support
- ended 12th April 2025
- PHP
- 8.1, end of life 31st Dec 2025
- Frontend
- Luma
- Security headers
- 2 of 6 present
- Hijack indicators
- none found
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.