Service
When the data should move by itself
Most companies do not have a systems problem. They have a person who moves numbers between systems, and that person is expensive, tired of it, and right about the same thing every time. An integration takes that job away from them and gives it to the two systems that already hold the numbers.
The work is not glamorous and it does not photograph well. It shows up as an error rate that falls and stays down.
This is the one service I will not put a number on before looking. The cost is decided by somebody else's API, and the difference between a documented one and an undocumented one is weeks. A review of your systems produces a written scope and one fixed figure, and that figure then holds like any other.
For scale, a full custom portal with its own roles, workflows and API connections starts at 7 500 €. A single connection between an existing store and one system is a fraction of that.
What usually gets connected
- ERP, meaning products, stock levels, prices, orders and the data an invoice is built from
- CRM, meaning enquiries, client records and the next step somebody owes the client
- Warehouse systems, meaning what is on the shelf, where it is, and who picked it
- Carriers and payment providers, meaning labels, tracking statuses and settled transactions
- Accounting, meaning the invoice raised once, in one place, and not typed again
Signs it is time
- Somebody exports a file from one system every morning and imports it into another
- Stock, orders and invoices disagree, and finding out which is right takes a person an hour
- A client asks where the order is, and answering means opening three screens
- The same customer exists twice, with different spelling, in two systems
What I need from you before quoting
The names and versions of the systems, whoever supports each one, and whatever API documentation exists. If there is none, say so early rather than late. An integration against an undocumented system is still possible, it simply costs what it costs, and you should hear that at the start.
Read access to a test copy is worth more than any description of the data. Half an hour in the real records answers questions that a specification never does.
What is not included
- Buying or licensing the ERP or CRM itself. I connect what you run, I do not resell it
- Changing how your ERP works internally. That belongs to whoever supplies and supports it
- Cleaning years of duplicate records by hand. I can write the rules that find them, deciding what to keep is your call
Delivered
Dispatch dashboard and single-pass warehouse routing
Picking errors from 28% to 0.3%
Touch interface usable in work gloves; no repeated walks across the hangar
The task. Warehouse staff retyped long part numbers on handheld terminals while wearing work gloves, and crossed enormous halls repeatedly, which produced long delays and a 28% picking error rate.
What I did. I built a picking dashboard that groups items by nearest hangar, aisle and shelf. Staff collect everything in one optimised pass through a high-contrast, single-tap interface, with no typing.
Measured by. Mis-picks per thousand lines, from the client stock logs, the quarter before and after.
Related
- Logistics and warehousing, where a wrong line costs money
- Online store development
- All case studies and how each one was measured
What to write so I can answer properly
I answer every email myself. If the first one carries the points below, the reply comes back with specifics and a price rather than with questions.
- What the business is and which country it operates in
- What you need, meaning services, a catalogue, a store or bookings
- What the goal is, meaning more enquiries, more orders or better visibility
- Whether a site exists today and what does not work about it
- When you need it live