Instead of Brandscope
Leave Brandscope. Own your wholesale order book.
Enterprise DNA builds your version around how your brand sells a season and refills stores between them, brings your Brandscope order files across, and runs it for you. The stockist list and the history stay in a database you control.
Brandscope does not publish its prices. Its FAQ describes an upfront fee to connect your ERP, then a flat monthly fee for unlimited users, with payment gateway fees on top, all quoted by its sales team.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the fees go
A Brandscope contract pays for a connection, a platform and a wait
The records underneath are simple: stores, the terms each one buys on, orders, credits and who sells to whom. Those belong to the brand. Most of the contract pays for the platform wrapped around them.
A project fee before you sell anything
The first charge is a one-off fee to wire your ERP into Brandscope for orders and stock. Brandscope says most of that work is bespoke, and the fee depends on which ERP you run.
Eight to twelve weeks to go live
Brandscope's own FAQ puts going live and visible to retailers at 8 to 12 weeks from project start. A season can be half gone by then.
A monthly fee set by your volumes
The flat monthly fee is quoted on your ERP, your brand and how many releases you put out.
Transaction fees on refill payments
Card and direct debit payments on refill orders run through the payment gateway, and those fees sit outside the monthly fee.
A marketplace you may not need
Part of what you pay for is a place where retailers browse brands. If your stockists already know you and buy through your reps, that is a feature you fund and rarely use.
Your stockist history on their system
Order files export as spreadsheet and CSV files. The full picture of who buys what, and how that has changed over five seasons, lives in their platform while you pay.
What you get instead
One wholesale book the brand owns, for reps, agents and the office
Stockists
Every store, its terms and whether it is still buying
Each stockist carries its own price list, its rep, its last order and its last visit. The office and the field read the same record.
- check Stores that have gone quiet
- check Which stores stopped carrying a line that similar stores still order
- check Each store's price list in one place, so a new season's terms are one change
- check Territories and reps side by side, so moving stores between two reps shows the effect on both first
The field
Reps and agents on a visible call cycle
Every store sits on its own visit cycle. See who is due, who is late and what each late store is worth.
- check Calls, strike rate and average order per rep, against the month's target
- check Visit notes and orders recorded against the store, not in a rep's inbox
- check Promotion checks in store: display up, ticket up, price right
- check A Monday review of the week written from the records
Orders
Orders at the right terms, handed to the ERP
An order comes out at the price list that store buys on, whoever writes it.
- check Orders in cases at the store's own price list, with any running promotion on the line
- check One step writes every submitted order out for your ERP and marks the batch sent
- check Orders that never went to the ERP stay on the attention list until someone clears them
- check Credits wait for authorisation, with batch codes kept on tracked lines
Yours
A database you own and can reshape by asking
The stockist list and every season's orders sit in plain records, readable by any tool you choose.
- check Add a field, a rule or a report by describing it in plain English
- check Order confirmations and rep weekly reports print with your brand name and logo
- check Open source under the MIT licence, so there is no vendor to leave
- check Your Brandscope order files brought across and checked on the way in
Make it yours
Design your own Brandscope replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Brandscope. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Brandscope data across and run it for you.
Switching
How to switch from Brandscope
Moving off Brandscope means getting your records out in the format your account allows, mapping them into the new database, and running a test before anything is switched off.
- 1
Export your records from Brandscope
Brandscope's own FAQ says order files export as spreadsheet and CSV files. Before you give notice, export whatever your account allows, usually CSV or Excel, and check with Brandscope if something you need is not covered. Get everything out while you still have access to the account.
- 2
Load the records in a test run
Brandscope's columns are not the same as the free version's import format, so the records get mapped on the way in. Run a test first. It shows exactly what would be created, your stores, contacts and orders, without writing anything to the database yet. Nothing is final until you look at the results and say so.
- 3
Check what the import flags
Read through what the test run reports before loading anything for real. It will point out records it cannot match, or history it has to skip. Decide what needs fixing, what to leave out, and what a person should check by hand before you run the real import.
- 4
Run both systems side by side
Keep Brandscope live for a short period while your reps and agents also work in the new system. Compare orders, credits and outlet records against what Brandscope shows for the same stretch of time. This is where you catch anything the import missed before you rely on the new system on its own.
- 5
Switch off Brandscope
Once the numbers match and your team is working comfortably without it, cancel Brandscope. Weigh separately whether the marketplace listing brought you real new accounts, since that is the one thing that does not carry across. The stores, orders, terms and credits themselves have already moved with you.
Where the real effort goes
The real work is mapping your own price terms, statuses and fields onto the new database, not the export itself. Brandscope's columns do not match the free version's import format, so someone has to decide how each field lines up and how much order history is worth bringing across. Enterprise DNA does this mapping, and the test run, when you have them install and run it for you.
Not ready for a call?
Get your Brandscope switch plan by email
We will send you the step-by-step plan for moving your business off Brandscope, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Brandscope switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to switch
Try the free version yourself, or have Enterprise DNA build and run yours
Open source
Run it yourself
Free
- 1 Download the free version from GitHub
- 2 Load the demo data and open it in Claude Code
- 3 Ask which stores need attention this week
- 4 Map your Brandscope order spreadsheets into it when you are ready
Omni by Enterprise DNA
Have Enterprise DNA build it for you
One setup fee, then a monthly retainer
- check We bring your stockists, price terms and order history across from Brandscope and check them against what you had
- check A branded ordering page for your stores, and a prebook screen for season buys, if your stockists order online today
- check We connect your ERP so orders go out to it
- check It runs inside Omni, our managed Command Center, with the rest of your business
Questions
Instead of Brandscope, answered
Our stockists place their own orders in Brandscope. What do they use instead? expand_more
The free version has no ordering portal for retailers. Orders come from your reps and agents, the office, and phone and email. If your stores are used to ordering online, Enterprise DNA builds your version a simple ordering page in your brand, reading the same price lists. You can keep a retailer portal for a season and move the reps, the reporting and the credits across first.
We sell by indent. Does this handle prebook? expand_more
A prebook order can be recorded against a store like any other order, at that store's terms. What the free version does not have is a visual assortment board for building a season's buy with the retailer. If your agents build buys that way, that screen is something Enterprise DNA builds into your version.
How do we get our history out of Brandscope? expand_more
Brandscope's FAQ says order files export as spreadsheet and CSV files. Export everything your account allows before you give notice. Their columns are not the free version's import format, so the records are mapped on the way in. Enterprise DNA does that mapping, and a test run shows what would be created before anything is written.
Will we lose retailers who found us on the Brandscope marketplace? expand_more
Stores that already buy from you stay your customers, and their details and order history come with you. What you give up is being listed where Brandscope's retailers browse for new brands. Count how many accounts actually came to you that way last year before deciding.
Brandscope takes card payments on refills. Does this? expand_more
No. The free version does not process payments. Invoices go through your ERP or accounts system and are collected the way you collect them now. If card payment on refill orders matters to your stores, raise it on the call and it is scoped into your version.
Keep your stockist book, not a platform contract
30 minutes with Sam. We go through what your Brandscope contract covers, what your reps, agents and stores actually use, and what your own version would look like. If it is a fit, we build it and run it. If it is not, take the free version and run it yourself.
Field Sales for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Brandscope?
Get your version built