CRM for Dropshipping: Orders, Suppliers and Margin
Dropshipping looks simple while there are ten orders a week. Then the real work begins: one order went to one supplier, the second to another, the third was cancelled, and the fourth is stuck without a tracking number. Requests sit in Direct, payments in a banking app, stock levels in someone else's price list. A dropshipping CRM is not decoration - it pulls these scattered pieces into one list where you can see every order and how much you actually earned on it.
How a dropshipping CRM differs from a regular one
A classic CRM is built around a deal with a client: contact, negotiation, payment. In dropshipping the centre of gravity is elsewhere - you have no warehouse, and half of the process happens on the supplier's side. So the order card here has to hold two chains at once: what you promised the customer and what the supplier actually did.
Hence the first requirement: every order needs a «supplier» field and its own status for that part of the process. The customer sees «order accepted», while inside the system it may mean «not passed on yet» or «passed on, waiting for shipment». When these two statuses are merged into one, the manager ends up checking everything by hand across chats.
The second difference is the product. In a regular shop the goods are yours and you control the stock. In dropshipping the stock belongs to someone else and changes without warning. So the system has to store not just the item name, but a link to it at the supplier, their price and the date it was last updated. Otherwise you will sell something that is already gone.
The third is money. You receive payment from the customer and pay the supplier separately, often in a different currency and on a different schedule. A system that does not keep these two amounts side by side within a single order shows turnover, not profit.
The order card: from request to tracking number
The basic unit of accounting in dropshipping is the order, not the client. The minimum set of fields is: what was ordered and how much, contact and delivery address, supplier, purchase price, selling price, payment status, supplier-side status and tracking number. That is enough to answer almost every daily question without opening a single chat.
Statuses are worth describing once and then leaving alone. A workable set: new, confirmed, passed to supplier, shipped, delivered, paid, cancelled, returned. Eight states cover everything, and behind each one stands a concrete action - either someone has to do something, or the order genuinely is waiting.
Record separately the moment an order moved to «passed to supplier». This is the main point where things get stuck. If there is no tracking number after twenty-four hours, the system should flag the order by itself instead of waiting for the customer to write.
The tracking number has to live in the card, not only in a message to the customer. Then the question «where is my order» is answered by a bot or a manager in seconds, with no need to dig through a two-week-old conversation.
Several suppliers in one system
One supplier is the starting stage. Then a second appears with better prices on part of the range, a third with faster shipping in its region, a fourth for a specific category. And here a spreadsheet stops working: each of them has their own price list, their own export format and their own rules.
In a CRM this is solved with a supplier directory. For each one you store the terms: how orders are passed on, how many hours until dispatch, which days are off, the minimum order value, how shipping is calculated and what happens with returns. This data is not for a report - it lets the system put a realistic deadline on the order instead of an optimistic one.
When one item is available from two suppliers, record a priority: primary and backup. Then, when something is out of stock, the manager does not search for an alternative from scratch but sees a ready option with its price and lead time. You also need a simple breakdown by supplier: how many shipped on time, how many were cancelled for lack of stock, how many came back. After two or three months it becomes obvious who is worth keeping.
Margin per order, not «on average»
The most common dropshipper mistake is to count the markup as a percentage and treat it as profit. The real margin on an order is the selling price minus the purchase, minus shipping, minus the payment processing fee, minus the advertising cost attributable to that order, minus losses on returns. Each of these looks like small change on its own, and together they eat half of it.
So keep every component in the order card: the purchase price, the shipping and the fees. Advertising is counted per channel over a period rather than per order, and then distributed - but even a rough estimate beats having none.
Once margin is counted per item, non-obvious things surface. Some products deliver good turnover and almost zero profit. Certain categories carry a high return rate that swallows the entire markup. One delivery direction is consistently loss-making because of refusals at the post office. This is exactly the report that tells you what to drop from the range and what to scale with advertising.
When spreadsheets are no longer enough and what to choose
Google Sheets honestly hold the first hundred orders. The signs that the limit has passed: you open several tabs to assemble one order; two people edit the same file and overwrite each other's rows; you cannot remember which orders are waiting for a tracking number; the margin report is assembled by hand at the end of the month and therefore never assembled at all.
Off-the-shelf CRMs cover part of the job, but almost all of them are built for classic sales. Supplier, purchase price and shipment status have to be bolted on as custom fields, and automatic hand-off of the order to the supplier has to be written on the side anyway.
The practical path is to move in steps: first a single order list with the full set of fields, then a bot or an intake form, then automatic hand-off to the supplier and tracking, and a margin report last. Each step closes a specific pain and pays for itself on its own. Devlly builds systems like this around a specific way of working: your suppliers, your statuses and your profit calculation, without modules that nobody in dropshipping will ever open.