Built by people who've lived the problem - for decades

Our Experience Didn't Start With PIM

Our journey began in the early 1990s, working inside large retail environments and implementing ERP systems alongside POS and WMS integrations.

Even then, the core challenge was familiar:

• •Getting accurate product information
• •Into the right systems
• •At the right time
• •So the business could trade

The tools were different.
The terminology didn't exist.

But the problem was exactly the same.

From Retail Systems to Supply Chains

Over the decades that followed, we worked across the full end-to-end supply chain - implementing and integrating ERP, WMS, POS, eCommerce, and PIM solutions.

By 2010, this experience culminated in large-scale PIM implementations, including work with Marks & Spencer using Stibo Systems STEP.

From there, we supported complex product data initiatives for organisations such as John Lewis, Sainsbury's, JD Sports, and Toolstation.

Across retailers, distributors, and suppliers, one pattern repeated again and again:

Product data problems don't show up as "data issues".
They show up as delayed listings, frustrated partners, operational drag, and lost revenue.

Seeing the Same Problems From Every Angle

Later, during the early growth phase of Pimberly, we worked end-to-end with customers — from early sales conversations through implementation and long-term support.

That experience reinforced what we already knew:

• •Most PIM projects are over-engineered
• •Too expensive for the value they deliver
• •Slow to adapt to real operational needs
• •And disconnected from how suppliers actually support downstream channels

We'd lived this reality from both sides:

• •Inside large retailers
• •And alongside the suppliers expected to feed them

Building What Should Have Existed All Along

Eventually, we stopped trying to force generic tools to work and built our own.

DataSauce was created as a fully-fledged PIM designed around how product information actually flows through real businesses, not how idealised process diagrams say it should.

Our first major customer was Evo Group, where we implemented a Vendor Portal solution in 2022.

Working closely with Evo Group, we:

• •Expanded their product catalogue from ~40,000 to over 110,000 products
• •Onboarded and supported more than 800 suppliers
• •Gained deep insight into the day-to-day challenges suppliers face when sharing product information

That experience directly led to VendorSauce.

Why VendorSauce Exists

Suppliers, manufacturers, and brand owners are now expected to support:

• •Resellers and wholesalers
• •Their own ecommerce channels
• •Marketplaces
• •Product or brand websites that redirect customers elsewhere

Often without controlling the final sale.

Yet product information is still managed through:

• •Spreadsheets
• •Emails
• •Manual updates
• •And multiple versions of the truth

VendorSauce exists to fix that.

It gives suppliers one trusted version of product truth and a practical way to share it confidently across all channels — without enterprise complexity or IT-only thinking.

What We Believe

We believe:

• •Product data is a commercial asset, not an IT problem
• •Suppliers should own and control one version of product truth
• •Multi-channel doesn't mean multi-spreadsheet
• •Tools should fit how businesses actually operate

Everything we build is informed by decades of real-world experience across the supply chain.

Not theory.
Not hype.

Just lessons learned the hard way — put to work.