DOMINUS
Every order checked. Every customer confirmed. Every product’s real profit, every day.
Cash-on-delivery dropshipping only works if the address is right, the customer knows the order is coming, and someone knows which products actually make money once returns land. Staff were doing all of that by hand across sheets and half a dozen tools. Dominus does it automatically, in every country, and stops for a human whenever it isn’t sure.
// How an order moves
- Capture Every order lands on the order sheet the moment it’s placed. Upsells are joined to the order they belong to.
- Verify The shipping address is checked against up to three validation sources. Anything unconfirmed is flagged for a person, never guessed. Gate · validated address
- Confirm One confirmation per order, in the customer’s language and currency, with the full total. A retry never sends a second message.
- Release Orders go to the warehouse only when the address is validated and the stock is there. Out-of-stock orders are tagged, not shipped. Gate · in stock
- Measure Profit per product from real outcomes: delivered, returned, still in transit, with product cost, shipping and daily ad spend.
// What the owner gets
The whole operation on a phone
Installable app with live sales per store, order status, delivery and return rates, per-product profit, and alerts before a problem costs a day.
Ask it, don’t dig for it
Ask by typing, speaking or sending a photo. It answers from the business’s own figures, answers only what was asked, and also answers the team in chat.
Describe it, it gets built
The owner describes a change to the app in plain words. It’s built, tested and deployed, and rolled back on its own if anything breaks.
Fixes first, alerts second
Before the daily warehouse cutoff it re-runs whatever can clear a problem, checks again from scratch, and alerts a person only about what’s left.
Each market runs on its own
Language, currency, address format and delivery rules are set per country, so a change for one market can’t break another.
Fits the tools you already use
Swapping a tool means rebuilding one connection. So far that’s meant moving support to a new helpdesk, taking a paid store platform out of the order path, and comparing messaging providers across every country.
An upstream tool quietly changed what it sent, and orders stopped qualifying for confirmation without a single error.
I rebuilt the trigger so “not done yet” is decided from the system’s own records, never from a field another tool writes, and added a supervisor that catches that whole class of failure. That’s the standard everywhere in Dominus: every skipped order is logged with a reason, and nothing fails silently.
- No shipment without a validated address
- One message per order
- Human approval on anything unusual
- Every skip logged with a reason
- Keys injected at runtime, never in code
- Private customer data stays private
Already used by a couple of dropshipping businesses selling into European markets. Europe is where Dominus started, not where it stops.