Apparel wholesale distribution

Your ERP was built for
forty orders a day.
This one runs four hundred.

Marketplace and channel volume does not fail your ERP in accounting. It fails it at intake, at reservation and at the picking floor. We build that contour as its own system on your server, leave your ERP as the ledger, and hand the whole thing to you in three weeks.

No call. No card. Five orders, five purchases, three minutes.

One order, end to end SO-1003 · Verde Concept Store
  • Order arrives from the channelone door per marketplace, costs frozen on arrival73 ms
  • Stock reserved across locationsavailability by bin, not by warehouse totalauto
  • Picked by barcodea box holds what was put in itfloor
  • Packed and labelledcarrier label printed from the pack screenfloor
  • Delivery note issuedall four Italian DDT shapesauto
  • Invoice raised and sent to SDIFatturaPA, fix and resend on rejectionauto
  • Written back to your ERPthe ledger stays where your accountant left itsync
Live reference build · invented data
Scope

What three weeks buys, and what it does not.

Three weeks does not buy your whole business, and any vendor who says it does is selling you an argument at the acceptance meeting. It buys one complete contour, working, on your data. The rest are further contours at the same price and the same three weeks each, in the order you choose.

Contour one: order to invoice

Three weeks
  • Channel and marketplace order intake, one door per channel, each opened deliberately
  • Commission, lead time and cost frozen on the order at the moment it arrives
  • Stock and reservation across multiple locations, with putaway and cycle counting
  • Pick, pack and box contents by barcode, on a screen that works on a tablet
  • Carrier label and all four Italian delivery note shapes
  • Customer invoice and the FatturaPA chain, including fix and resend
  • Per person logins and six roles enforced in the database
  • Two way sync with the ERP you already run

At the end of week three your team works a real day in it, beside the old system. If they cannot, you do not pay.

Later contours

Three weeks each
  • Purchasing, vendor bills and three way match
  • General ledger, VAT registers, fiscal close and the parallel run
  • Treasury, bank statement matching and collections
  • The sale event calendar and the acquisition funnel
  • Reporting with the analytic dimension your ERP never wrote
  • People, attendance and time off
  • Your own marketplace storefront on top of the same catalogue

All of these are built. They are listed here as separate contours because sequencing them is your decision, not ours, and because accounting should be the last thing to move, never the first.

The demo

Five orders. Five purchases. One complete day.

Sign in as the person whose job you want to check. Sales sees orders and margin, the warehouse sees the pick in front of it, purchasing sees what is at the dock, finance sees what can be sent to SDI tonight. Same system, four different days.

Sales

Five orders, one of them mid pick

Follow SO-1003 from the channel to the invoice without leaving the document. Margin per line is computed, not typed.

Warehouse

The pick that belongs to that order

PICK-441 on a full screen scan view with no application chrome, forty eight pixel targets, and a keypad for when the gun is flat.

Finance

The invoice that comes out of it

INV-3001 with its journal items, its SDI lifecycle and a bill that failed three way match sitting next to it.

Open the live demo This is a reference build on invented data. Yours will be different, because it will be yours.
What it connects to

Nothing you already run gets replaced.

The reason a three week delivery is possible at all is that we do not migrate your accounting, your history or your fiscal setup. Your ERP keeps being the book of record. We take the operation off its back.

Stays yours

Your ERP is the ledger

Odoo, SAP, an old Italian package, it does not matter. Documents flow back to it, and your accountant keeps working the way they work today.

  • Odoo 14 to 19
  • SAP
  • Legacy Italian ERP
  • Read only sync
Comes in

Channels, catalogue, carriers

One intake door per channel, defaulting to off, so nothing arrives until you deliberately open it. Product data from your PIM, labels from the carrier you already use.

  • Marketplaces
  • PIM
  • FedEx
  • ShippyPro
  • ZPL printing
Goes out

The Italian fiscal chain

Delivery notes, FatturaPA, SDI lifecycle in the interface rather than in an inbox, and a hash chained audit trail underneath all of it.

  • DDT
  • FatturaPA
  • SDI
  • PEC
  • Conservazione
Evidence

Measured on the reference build, not estimated.

Your technical people will ask harder questions than your buyers will. These are the answers we can put a number on.

0
To accept a channel order including the full stock chain, against a two second budget
0
Sales channels mapped, each with its own commission, lead time and document shape
0
To load 1.37 million rows into a fresh environment, at their production volumes
0
Automated checks that run before any change can reach production
Straight answers

The six questions everyone asks in the first call.

We already have an ERP. Why would we add another system?+
You would not, and we would not sell you one. Your ERP is where your accountant, your fiscal history and your auditors live, and moving that is a year of risk for no gain. What we replace is the part it was never designed for: hundreds of small channel orders a day, reservation by bin, and a picking floor working on a tablet. The ledger stays exactly where it is.
Three weeks is not a credible number for an ERP.+
It is not a credible number for a whole ERP, which is why we do not claim it. Three weeks is one contour, named on this page, on your data, with your team working a real day in it at the end. The reason it is possible is that the domain is already built and the price of writing software has collapsed. If week three ends and you do not accept it, you do not pay.
What happens when you leave? We are not a software company.+
One of your people holds the repository, and we spend the last week teaching them to change it with an AI agent, not teaching them to code. They ship three real changes with us in the room, and they roll a release back themselves before we go. Underneath, a test suite and a merge gate stop that agent from breaking the second thing while it fixes the first. The worst thing your AI can do is open a change that fails a check.
What if we want you to stay?+
Then you keep the engineering retainer, which tapers over six months by default and can simply not taper. What you cannot do is end up dependent by accident. The last day is written into the contract on the first day, and you have to actively decide to move it.
Where does our data sit, and who can see it?+
During the build, on hardened infrastructure in the European Union. After handover, on your server, in accounts you own, and not on ours at all. Access is per person, roles are enforced in the database rather than only on screen, and every write is attributable to a name. A mutual NDA and a GDPR processing agreement are signed before we probe anything.
What does it actually cost, all in, in year one?+
One contour built at €10,000, plus €1,000 a month to run it, is €22,000 for the whole first year. Every number is fixed before we start. There are no seats, no per user pricing, no implementation fee on top, and no module you discover you have to buy in month four. Compare that with the setup fee alone on the quote sitting next to this one.
Pricing

Per contour, not per seat.

Adding people to a system you own should not cost you anything, so it does not. What costs money is us building and running it, and that is the whole of what you pay for.

Contour one, order to invoice

€10,000
Once · fixed · three weeks

On your server, with the source. The probe that produces the scope is free, and the fee comes back if your team cannot work a real day in it at the end of week three.

Running it with you

€1,000
Per month · cancel any month

Building, incidents, updates, the Italian fiscal changes, improvements to the shared apparel core, and teaching your person to hold it. Stop it and everything keeps running.

Signing on the first of September, the whole year to the first of September costs €22,000. Year two is €12,000 if you keep us and nothing if you do not.

Three minutes in the demo
beats an hour on a call.

Five orders, five purchases, four roles, and one order that goes all the way through. If that does not answer your question, book the call and bring your hardest one.

Open the live demo Book a technical call No call. No card. Thirty seconds.