Customers and resellers
- Customer records with CSV import
- Reseller accounts and reseller sales
- A customer self-service portal for subscriptions, billing, profile and contact
Client build · Custom ERP and website
StoryLine is an IPTV business in Denmark. We built its ERP, a web app that keeps customers, resellers, subscriptions, stock, sales and invoices in one place and takes payments through MobilePay, Revolut and Stripe. We also built its WordPress website, storyline.help, whose WooCommerce orders flow straight into the ERP without anyone retyping them.
The problem
A subscription business with resellers has a lot of moving parts. StoryLine sells subscriptions to customers directly and through resellers, keeps stock of digital codes and TV boxes, buys from suppliers and has to remind every customer before a renewal is due. Those records lived in separate places, and orders placed on the website had to be copied over by hand.
Danish customers expect to pay with MobilePay, so card payments alone were not enough, and the business also uses Revolut. The team needed one system where a sale, its payment, the subscription it starts and the stock it uses are all linked, and where customers can look after their own subscriptions instead of writing in.
Constraints
The ERP is single-tenant: it runs for StoryLine alone, and our own billing as the software vendor never appears inside the client's app.
MobilePay, Revolut and Stripe are connected with the client's own accounts, so customer money goes straight to StoryLine.
Danish kroner are the default currency, the interface switches between English and Danish, and exchange rates are fetched with the krone as the base.
Owner, manager and customer-service roles are enforced with row-level security in the database, not only in the interface. A security review moved every secret out of the browser and into server-side functions.
What we built
The ERP is a React and TypeScript app on Supabase (Postgres, Auth with magic links or passwords, and edge functions), hosted on Netlify.
The codebase went through a standardisation pass in November 2025 that brought every module onto the same structure and naming, and a later major release added team roles and settings screens. Payment settings for MobilePay and Revolut live in the ERP's own settings screens, so the client can change them without a developer.
Order
Placed on storyline.help
WooCommerce webhook
Customer and sale created in the ERP
Payment link
MobilePay, Revolut or Stripe
Webhook confirms
Payment recorded
Subscription runs
Visible in the customer portal
Renewal reminder
Sent by the daily job
Handover
StoryLine runs the ERP under a licence and support arrangement with us, so the handover is a working set of documents rather than a one-off file drop.
Status and link
Live. The ERP is a private staff app, so we link only the public website. We keep maintaining the system and ship changes as the business needs them.
Visit storyline.help (opens in a new tab)What we leave out
No screenshots: every screen of a working ERP shows real customers, so we would rather describe the modules than blur them. No customer numbers, sales figures or prices either. They belong to the client.
Next step
Tell us what you have today and what should change. We reply within one business day. You get a written scope and a fixed quote before anything is built.