Add-Ins · Catalogue and stock
One Product Record, Consistent Everywhere.
Most catalogue problems start with the same product existing four times: once with each supplier, once in the store and once in the accounting system. We build a single internal record for each product and keep the rest of the systems tied to it.
That record carries your SKU, your pricing rules and your publishing decisions, while supplier identifiers stay in the background where they are needed for reordering and matching.
Pricing, tax and publishing rules are configured with you and tested on a sample of real products. They are not applied to the whole catalogue until you have seen the result.
01 · Capability
One internal record per product
Supplier catalogues are read and matched into your own product records, so staff work from one list rather than several overlapping ones.
- Internal product SKU mapping, with supplier identifiers retained in the backend
- Multiple suppliers linked to a single product, with a preferred supplier rule
- Duplicate detection and catalogue cleanup, including products that already exist more than once
- Product matching by manufacturer part number, supplier SKU or agreed matching rules
- Category mapping from supplier taxonomies into your own
- New, changed and discontinued product reporting, so a review can be considered rather than assumed
02 · Capability
Pricing controls
Cost price, selling price and recommended retail price are three different numbers. The rules below keep them separate, so a cost update does not quietly change what customers are charged.
- Price markups, minimum margins and channel-specific rules
- Correct handling of GST-inclusive and GST-exclusive supplier data
- Separate handling of cost price, selling price and recommended retail price
- Rounding rules and freight treatment agreed with you
- Minimum margin floors, so a product is held back rather than sold below your limit
- Price change history, with the source of each change recorded
03 · Capability
Stock and publishing controls
Stock figures and publishing decisions are controlled rather than assumed, which is what keeps an out-of-stock product off a sales channel.
- Out-of-stock and zero-price product controls
- Stock buffers for fast-moving lines sold on more than one channel
- Product exclusions and publishing approvals
- Channel-level publishing rules, so a product can appear in one channel and not another
- Suspensions and reinstatements recorded in the synchronisation log
04 · Capability
Synchronisation, logs and notifications
When a catalogue runs on a schedule, the schedule itself has to be visible, because a silent failure looks exactly like a quiet week.
- Synchronisation schedules matched to how each source publishes its data
- Event-based updates where the source supports them
- Run logs showing what changed, what was skipped and why
- Error notifications when a feed changes format, a product cannot be matched or a rule fails
- Review queues for records that need a person to decide
Optional
AI-assisted catalogue work
AI is optional and used to prepare work for review. It does not publish products, set prices or decide what a customer sees.
- Suggesting product categories
- Matching similar products across supplier catalogues
- Identifying incomplete or inconsistent product information
- Drafting product descriptions for review
- Flagging unusual price and stock changes
Each of these requires validation against your own data and business rules before it is relied on, and every suggestion waits for a person to accept or reject it.
How it works
Discover, connect, configure, test, then launch
Catalogue work follows the same five steps as every Add-In. Discovery is where we assess how messy the current product data is and how much cleanup is realistic.
Discover
We look at your catalogue, the supplier feeds behind it, duplicate products, current pricing rules and the GST treatment used today.
Connect
Supplier feeds, store catalogues and accounting systems are connected through supported access, with data licensing limits respected.
Configure
SKU mapping, matching rules, margin logic, category mapping and publishing approvals are configured and reviewed with you.
Test
A sample of products runs through the full path, including a cost change, a discontinued line and a product that should not be published.
Launch and support
The catalogue syncs on schedule with logs and error notifications, and we review the first update cycles with you before handing over runbooks.
Product Catalogue & Inventory Sync questions
No, but the cleanup has to happen at some point. We usually do it during the project, starting with duplicate product records and missing identifiers, because matched products are what make the rest of the workflow reliable.
Only if you have configured it that way. Cost updates and selling price changes are separate steps, and margin floors can hold a product back rather than let it sell below your limit.
Supplier data is read as published, whether that is GST-inclusive or GST-exclusive, and converted to the treatment you have agreed with your accountant before any margin or price rule is applied.
It can draft them, and they stay as drafts until someone approves them. We never publish generated product claims, specifications or stock figures without a person checking them against the source data.
Related Add-Ins and services
Product Catalogue & Inventory Sync enquiry
Tell us what to connect
Share the platforms, suppliers, marketplaces and systems you use, and the workflow that costs the most time today. We will come back with what each one allows and what an integration would involve.
- A written assessment before any build starts
- Access through supported authentication, never a password
- Your data, mappings and documentation stay yours
Prefer the general form? Use the contact page or call 0800 00 2270.
Start with the assessment
Tell us what you use and what you want connected. We will tell you what can be automated, what has to stay manual, and what it would take.