Skip to content

Client build · Custom ERP and website

StoryLine: ERP and website for an IPTV business (Denmark)

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

What needed solving

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

What the build had to respect

  • One business per install

    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.

  • Payments go to the client

    MobilePay, Revolut and Stripe are connected with the client's own accounts, so customer money goes straight to StoryLine.

  • Built for Denmark

    Danish kroner are the default currency, the interface switches between English and Danish, and exchange rates are fetched with the krone as the base.

  • Staff see what their role allows

    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 build, part by part

The ERP is a React and TypeScript app on Supabase (Postgres, Auth with magic links or passwords, and edge functions), hosted on Netlify.

Customers and resellers

  • Customer records with CSV import
  • Reseller accounts and reseller sales
  • A customer self-service portal for subscriptions, billing, profile and contact

Sales, invoices and reporting

  • One sales module and one purchases module for every channel
  • Invoices with public invoice pages a customer can open and pay
  • A dashboard with a profit overview, plus data export

Subscriptions and stock

  • Subscription products and renewals, with a daily reminder job
  • Recurring MobilePay renewals
  • Inventory of digital codes and TV boxes, suppliers and purchases

Email

  • Email templates, including welcome and renewal-reminder emails
  • A pending-email queue and a log of everything sent
  • Sending through Brevo from storyline.help addresses

The website

  • storyline.help on WordPress with WooCommerce
  • A WooCommerce order webhook that creates the customer and the sale in the ERP

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.

From a website order to a renewal
  1. Order

    Placed on storyline.help

  2. WooCommerce webhook

    Customer and sale created in the ERP

  3. Payment link

    MobilePay, Revolut or Stripe

  4. Webhook confirms

    Payment recorded

  5. Subscription runs

    Visible in the customer portal

  6. Renewal reminder

    Sent by the daily job

Stack and integrations

App
  • React
  • TypeScript
  • Vite
  • Tailwind
Backend
  • Supabase Postgres
  • Edge functions
  • Netlify functions
  • Scheduled jobs
Payments
  • MobilePay
  • Revolut
  • Stripe
Website and email
  • WordPress
  • WooCommerce
  • Brevo

Handover

Handover and support

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.

  • A deployment guide for the app and its functions
  • MobilePay and WooCommerce integration guides, including the webhook setup
  • Guides for the scheduled heartbeat that keeps the database active
  • A security review report and the fixes that followed it
  • Release notes for each major version

Status and link

Where it stands

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

What we do not publish

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.