
Custom work · tarpaulins and shade cloths, NL and DE
From 2,215 separate product pages to about 250 families.
Afdekzeilwinkel sells tarpaulins and shade cloths in dozens of sizes and colors, in a Dutch and a German store. We built a PIM that does more than store content: it speeds up the work.
- Items
- 2,215
- Families detected
- 259
- Stores
- NL (Lightspeed) and DE (Shopify)
- To the German store
- 356 products
The problem
Nearly the same text, sixty times over.
Picqer held the items, Lightspeed the Dutch store and Shopify the German one. Every product had its own texts for each store, even when it only differed in size or color.
Titles in Picqer and Lightspeed sometimes contradicted each other, and 356 products were not yet in the German store.
Families
Write once, right 51 times.
The system reads every title and proposes families. PE Standard tarp in 51 sizes and colors becomes one page to manage.
The template fills in the size and color for each item, so every item keeps its own page in the store. Managed together, published separately.
Product knowledge
Product knowledge with a source.
What a product is, how long it lasts, how you fasten it and what it isn't for: captured in eight fixed topics.
The AI proposes facts from the existing store text, and every proposal carries a verbatim quote. What can't be backed up doesn't go in.
AI assistant
Tell the assistant.
A fact about the product becomes product knowledge. An instruction about writing becomes a rule, and you see what that rule does first.
Text proposals arrive as cards: accept, reject or edit. The AI can never publish by itself.
German for Shopify
The German store keeps up automatically.
Translated into German field by field, in the store's own voice and with fixed terms. The Shopify store's filters and product fields are filled correctly straight away.
When the Dutch text changes, the team sees exactly which German field needs redoing.
Safe publishing
So nothing goes wrong.
Checks before you look
Forbidden phrases, numbers without a source and broken variables are caught before a text reaches the team.
See first, then publish
For each item, you see exactly what goes to the store. Publishing everything at once is deliberately not possible.
You can always go back
Before overwriting, the system takes a snapshot of what was live.
Where we are now
Roadmap
In use by the team. The rollout is under way, family by family.
- July 2026
Dutch to German
The first version: the products from both stores in one place, and translation into German for the Shopify store.
One place for both stores.
- August 2026
The PIM
Families, templates per channel and the publishing engine, built the way the team wanted.
Managing by family instead of by item.
- September 2026
Product knowledge and assistant
Knowledge with a source, the assistant on every product page and publishing to both stores.
In use by the team.
- Now
Rollout
Families are being bundled and filled. The first publications to the stores are ready.
Next: live, family by family.
Sound familiar?
How many of your product texts are actually almost the same?
Many online stores manage every size and color as a separate product. Book an intro call and hear in 30 minutes where your time goes, and what we can build for it.
More cases
Read on.

Own brand · Shopify Plus · 12 languages
~€105
to translate the whole store
The complete store in 12 languages, in its own voice.
Products, collections, pages and FAQ. Translating a product takes 30 seconds instead of 15 minutes. No agency, no freelancers.
“It used to take weeks to launch a product because we were waiting for translations. Now that happens in a morning.”
Arjan Spakman · ETQ Amsterdam - Content & translation

Custom · yacht charter, Aruba
7 weeks
from the start of the build to running on live data
Booking, calendar and money side by side.
Let's Book, Google Calendar and the boats' GPS in one place, for the office, the captain and the crew. Differences stand out right away, and the crew runs checklists on the phone.