ERP
When a multi-brand seller needs their own ERP
A shipping tool tracks a parcel. A spreadsheet tracks a promise. Neither one knows that two brands must not see each other's orders, or that a return has to come back through the warehouse and into stock. That is the gap a custom ERP fills.
Hector processes 200 to 300 orders a day across the marketplaces, and the reports come out in one click.
Who this is for
The fit is a founder or operations lead whose team has outgrown copying orders between a marketplace, a sheet, and a carrier. A one-page marketing site is a different job. The work here is the system the team opens every day: orders, stock, purchasing, and who is allowed to see which brand.
Hector runs that for more than one brand on one platform. Each brand's orders, stock, and users stay isolated. Multi-brand is the business. Isolation is how the data is separated.
What the first system has to include
Order intake from the channels you actually sell on. A stock ledger, not a cell someone overwrites. Purchasing and inbound receiving if product is still arriving while you ship. A role for the person on the floor, and a different role for the person reading the report.
Hector also covers returns, reshipment, repair, trade-ins, payroll, and attendance, because the same company was already doing that work in other tools. A new build does not have to start with all of it. It has to start with the handoff that is failing.
Proof, and who owns it
The production system is Hector, built while I was a full-stack engineer at Retrovgames. The platform belongs to them. Three to four people were on the manual order flow. It now runs with one person, at 200 to 300 orders a day, with reports from the same system.
The customer portals for those brands are separate apps. A shopper signs in, then tracks an order, starts a return, downloads an invoice, or submits a trade-in. Those apps are at app.retrofam.com and app.retrovgames.com.