The pain and the solution
The pain
- In fulfilment, leads sit in a CRM, the warehouse in spreadsheets, shipments in marketplace dashboards and invoices in accounting, all reconciled by hand.
- Receiving without a discrepancy report turns into an argument with the seller over how much was delivered.
- What the warehouse work cost for each seller is worked out at month end from memory and spreadsheets.
How we solved it
- One system in five parts: website, CRM, warehouse system, portals and admin.
- The path from request to seller to goods in stock to shipment to money runs without manual transfers.
- Every warehouse operation becomes a charge at the seller's rate, and the seller's invoice is built from them.
Recognise your task? We will solve it for you too.
Discuss a similar projectWhat we did
Website and CRM
A site with services, rates and a calculator, a pipeline from request to contract, lead sources and ad tags.
Warehouse
Supply requests, receiving at the gate with a discrepancy report, addressed storage, picking, packing, shipping and returns.
Billing
Every warehouse operation becomes a charge at the seller's rate, and invoices and acts are assembled from those charges.
Role portals
Seller, receiver, storekeeper, logistics, manager and administrator work in one portal, each with their own rights.
Marketplaces
Exchange with marketplaces: orders, shipments and stock without manual exports.
The project in detail
FullHouse is a fulfilment operator: it takes marketplace sellers’ goods into its warehouse, stores them, picks orders and ships to marketplaces and other platforms. We are building it together with its own software, so it runs on it from day one.
Two flows
The system has two main flows. The first is the customer’s path: advertising, the website, a request or sign-up, a manager taking the lead through the pipeline, a contract, and the person becomes a seller in the system. The second is the goods’ path: the seller creates a supply request in the portal, the warehouse receives the goods, places them in cells, picks orders, ships to the marketplace and takes returns. Every warehouse operation immediately becomes a charge for the invoice.
What it is made of
A website with services, rates, a calculator, cases and a blog. A CRM with a pipeline, touchpoints, lead sources and ad tags. A warehouse system: receiving at the gate with a discrepancy report, addressed storage, transfers and stocktaking, picking and packing, shipping, returns with a quality check. Billing at the seller’s rates. Exchange with marketplaces. An admin area where the team edits site content, prices, notification templates and rights.
Prices live in one place: the calculator on the site and the warehouse charges use the same price list, so a seller never sees one price on the site and another on the invoice. Signing contracts through Telegram is designed in from the start.
How we build it
The work is split into modules, and each has a written contract with its neighbours: what receiving hands to storage, what shipping hands to returns, which events go to billing. Website with CRM and receiving come first, then storage, shipping, returns, billing and marketplaces.
Who it fits
Fulfilment operators and storage warehouses, and marketplace sellers with their own warehouse who need warehouse software built around their processes instead of a boxed product.
Materials about the project
Marketplace integration: orders, stock and prices in one system with your warehouse
What to pull from a marketplace and what to send back, when a 1C module is enough and when you need your own link, and where sellers lose money without one.
Warehouse automation: from a spreadsheet to your own warehouse software
When a spreadsheet stops coping with a warehouse, what receiving with discrepancy reports, batches, cells and QR codes give, and 1C versus custom software.
Discuss a similar project
Tell us about your task, and we will suggest how to build something like this for you.
- 01Analysis
We study processes, data and the points where value is lost, and fix the result we are working towards.
- 02Architecture and prototype
We design the system and build the first version on your real data. Stages and cost are agreed before work begins.
- 03Pilot
We launch in one area. Every stage is checked in a test version before it goes into operation.
- 04Scale and support
We connect the remaining areas, take responsibility for how the system runs and keep developing it.





