A price comparison engine, and what it became
A price engine over a thousand sources, a vouchers and offers business, and a WordPress blog showing live prices in its posts
- Client
- MeltBrands
A price comparison site is a data product wearing a shopfront. ShopBoxUK compared prices across more than a thousand online sources for UK shoppers, and over three years it grew from a comparison site into a vouchers and offers business, with its prices also feeding the ShopBoxUK blog. Toobler engineered all of it.
Customer and context
MeltBrands UK came to Toobler to build its price search engine, ShopBoxUK. The premise was simple to say and hard to do: collect current prices from over a thousand online sources across consumer products, and put the best one in front of a shopper. The alternative, as the original brief put it, was a person visiting a thousand websites and comparing by hand.
Toobler engineered it from 2012 to 2015: the comparison site, the admin behind it, the voucher product that grew out of it, and the WordPress plugins that bring the site’s prices into the ShopBoxUK blog.
The challenge
- A catalog assembled from a thousand strangers. Every source has its own feed, its own categories and its own idea of what a product is. None of that is the shopper’s problem, so all of it has to be reconciled before a page renders.
- Browsing is the hard screen. Thousands of products with photos, at different sizes, have to be scannable at a glance and still let someone get quickly to the one thing they came for, without the grid rearranging itself every time the window moves.
- A price site lives on category pages. If search engines can’t see the catalog’s structure, the catalog doesn’t get found.
- The product kept changing shape. A price engine became a price engine plus vouchers plus live prices in the blog. Each addition reached back into the same data rather than sitting beside it.
- Money attracts attention. Anything handling user accounts around retail traffic has to assume someone will try the obvious attacks.
The solution
Feed ingestion, normalized into one catalog. XML parsing with its own test pass, data pulled from the API into category and brand tables, and a site menu generated by parsing the API rather than maintained by hand, so a change in the source data changed the navigation.
A browsing grid built for the problem. The team used the Isotope jQuery plugin and wrote a custom layout mode for it, plus an isoRepeat directive and a price filter in AngularJS. Lazy loading had to be implemented without image dimensions, because the ShopBox API didn’t supply them. The explicit goal was to minimize how much the content rearranged itself on resize: the difference between a grid you can shop and one that moves under your hand.
Vouchers and offers, built as their own product. Voucher administration with its own categories, icons and types, multi-level category mapping, retailer listing pages carrying special offers, and in-stock or out-of-stock state rendered live from the API. Nearly forty tasks across three work streams made this a second product line, not a feature.
Search-engine surface treated as infrastructure. Category pages, a sitemap carrying third-level categories, and work explicitly aimed at making the site indexable. A comparison site that can’t be crawled can’t be found.
Live prices inside the blog. Toobler built two WordPress plugins that put ShopBoxUK prices into posts on the company’s blog, pulled from the catalog through its API. With the Lowest Price plugin, an editor picks a product category at up to three levels and places it in a post with a shortcode; readers see the lowest current prices in that category. With the Dynamic Price plugin, an editor searches the catalog and ticks the specific products to feature. Because prices load when the page does, a post written months earlier still shows today’s prices.
Security as a work stream, not an afterthought. XSRF protection in AngularJS, with a token in a JavaScript-readable cookie echoed back as a header and verified server-side. The token itself is a digest of the authentication cookie, so it can’t be forged by script. Alongside it: a content security policy, random token generation, and regression testing across the application.
A PHP backend behind the AngularJS front end, moved onto CodeIgniter. The comparison site’s interface is built in AngularJS. Behind it, a PHP backend reads the ShopBox API on scheduled cron jobs and fills the category, brand and menu tables the interface reads from. In late 2013, as part of the security work, the team moved that backend from plain PHP onto the CodeIgniter framework, re-set and verified the cron jobs, added unit tests, and removed the leftover plain-PHP files. The blog stayed on WordPress.
Results
ShopBoxUK ran as a price comparison service with its own vouchers and offers business, with live prices from the same catalog in its blog, built and evolved by one team across more than three years.
The useful part is the shape of the engagement rather than any single feature. A product that begins as “compare prices” and grows into “compare prices and run offers” needed an engineering team willing to rebuild its own foundations partway through, and to add new parts without breaking the first.
This is a build of its time: AngularJS 1.x and jQuery on the front end, PHP and CodeIgniter behind it, and WordPress plugins as the bridge between the blog and the catalog. The pattern isn’t: a data product that has to be ingested, made browsable, made findable, and then put to work wherever the business publishes.
The guys at Toobler were very involved from the very first minute they started working on my project. Their commitment, knowledge and dedication helped me wrap it up in a spectacular fashion and needless to say, the result was a huge success.

Lee Barrett
MeltBrands
Related work and capabilities
- Case study E-commerce · Marketplace
A two-sided marketplace, built for sneakers
How Toobler built ShoeperMarket — a dedicated two-sided marketplace for buying and selling shoes: Solr-powered catalog search, offers, a demand-capturing Hunt List with smart matching, and full seller and buyer flows.
- Industry
E-commerce & Marketplaces
How you sell is specific to you, and a template store makes you sell the way it was configured. Toobler builds the stores, marketplaces, catalog search, checkout and integrations commerce businesses run on.
Proof, engineered
Case studies from Toobler — real platforms engineered across event technology, construction and digital twins. The work behind the claims.