Keep one item list that billing, stores and reports all read from.
Product management is the item list everything else reads from: one code per item, its units, its variants, its rates and its tax code. Add a product once, and the counter, the store and the reports all use the same entry. Stock counts stop disagreeing with sales because two people were billing two spellings of the same thing.
Ask three people in the shop for the rate of a 4 by 8 sheet and you may get three answers. The counter has an item, the store has another with a longer name, and the salesperson has one created last festival season. All three are the same plywood.
Here it is one item with one code, entered once. Variants sit under it and not beside it, so brown and white are two options of one product and not two products. Whatever you change here shows up wherever that item is used.
What your team uses today.
The module takes over these, one at a time, so nothing has to stop while it is set up.
- The item list in a spreadsheet
- Price lists printed and pinned up
- Product names jotted in the billing screen
The problems this is meant to ease.
What product management does.
What this looks like in a working week.
Illustrative scenarios, written to show the shape of the work. They are not accounts of client systems.
The people who open this every day.
From first conversation to daily use.
Reading the current list
We look at your sheet and counter software. You provide an export, and we report on duplicates and gaps.
Codes and categories
A coding scheme and categories are proposed. You approve them before anything is loaded.
Cleaning together
Duplicates are merged with your staff. Each decision is logged for later reference.
Trial import
A sample of items is loaded into a test copy. You check units, rates and tax codes.
Switch to the shared list
Billing and stores read from the new list. A short session for each team closes the step.
How you would know it is working.
Record where you stand before it goes live, so the change is measured against your own figures.
- Duplicate items found in periodic checks
- Items without a rate or a tax code
- Variants with stock but no rate
- Items created by each user
- Retired items still appearing on new bills
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Stock tracking and alerts
- Point of sale billing
- Purchase order management
- Barcodes and labels
- Accounting software
Products that include it.
How we would put it in.
Questions owners ask about product management.
Do we key in eight thousand items again?
No. Your list comes across from your accounting software, from your billing software or from Excel, with codes, rates and tax details. Your own people check a sample before anything goes live, because the rates are yours and not ours.
Can two customers have two different rates for one item?
Yes. A dealer price list, a retail rate and a special rate for one builder can all sit against the same item, and the right one appears when you pick the customer.
Is an Excel item list enough?
For a shop with two hundred items and one person billing, yes. Excel gives up at two counters billing at once, or when a rate change has to reach the warehouse and the shop on the same afternoon. Our furniture showroom software keeps models, sizes, fabric codes and finishes under one product in exactly this way.
What about duplicates we already have?
They are merged during the set-up, with somebody from your side deciding which entry survives. Nobody enjoys that week, and it only has to be done once.
What pushes up the cost of an item master?
Item count, variants and price lists drive it. Tax setup comes next. Links to billing and stock add detail. A sample of your list is read, then each piece is costed apart, so a piece can be taken out.
What governs how long cleaning the list takes?
It depends on duplication in your present list. Early use needs items, variants, units and rates. Calendar dates follow the sample review.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle product management today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
What happens after you share your requirements
- A senior engineer reads your answers. Nobody phones first.
- Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
- If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
- No call is booked and nothing is paid until you have read the note. Your details stay with us.
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirements