labs@atheron:~/industries/franchises/integrations$ connect --systems --automate

Royalty reporting

Sales from every POS, royalties without retyping.

Royalty day should be a report. When sales come straight from each location's point of sale, nobody retypes figures and head office stops checking spreadsheets against POS exports. We build the integration service, the calculation and the statements, on each vendor's published API.

Start a project See the example projects

// what matters here

What is different in this industry.

Straight from the POS

Daily sales read through each POS vendor's API, even when locations run different systems.

Your agreement terms

Royalties and fund contributions worked out to the terms in your agreements, including exceptions by location.

Statements franchisees trust

Each franchisee sees the sales behind their statement and can question a figure before it is invoiced.

Into your books

Invoices and payments posted to QuickBooks Online, built on its API.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appAPI

Royalty reporting from POS

Hypothetical. Not a client, not a result.

// The problem

A franchisor's locations run three different POS systems, franchisees type their monthly sales into a spreadsheet, and head office spends the first week of every month checking figures before it can invoice royalties and marketing fund contributions.

// What we would build

An integration service that reads daily sales from each POS through its published API, a calculation of royalties and marketing fund contributions to the terms in your franchise agreements, statements each franchisee can see and question, and invoices posted to QuickBooks Online. We check your POS vendors' APIs before we quote. Your agreements and your accountant set the rules; we give no legal or tax advice.

// What is in it

Daily sales read from each POS system through its API
Royalties and marketing fund contributions worked out to your agreement terms
Monthly statements franchisees can see, question and accept
Invoices and payments posted to QuickBooks Online
Alerts when a location's sales stop arriving
An internal API documented with OpenAPI, for the next system that needs the figures

// Stack

Node.js
PostgreSQL
POS vendor APIs
QuickBooks Online API
OpenAPI
AWS Canada

// estimate

Build: ≈ US$124,000 to US$190,000, delivered within 33 weeksCAD 176,500 to 269,900
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data mapping and sandbox connection: 0.4 weeks
Design approved: 2.4 to 3.4 weeks
API contract agreed: 1.4 to 2.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Sync built and reconciled in sandbox: 1.9 to 2.9 weeks
Core resources built: 2.9 to 4.9 weeks
Security, gateway and connections: 1.9 to 3.4 weeks
Testing and fixes: 0.4 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Royalties reconciled against a past period: 1.4 to 1.9 weeks
Launch: 0.9 to 1.4 weeks
Live cutover: 0.9 to 1.4 weeks
Hypercare: 0.9 to 1.4 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

POS API access from each vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 35,300 to 53,980
Discovery 1.4%: CAD 2,471.00 to 3,778.60
Data mapping and sandbox connection 2.1%: CAD 3,706.50 to 5,667.90
Design approved 1.4%: CAD 2,471.00 to 3,778.60
API contract agreed 4.3%: CAD 7,589.50 to 11,605.70
Core features 4.4%: CAD 7,766.00 to 11,875.60
Full build 2.9%: CAD 5,118.50 to 7,827.10
Sync built and reconciled in sandbox 6.4%: CAD 11,296.00 to 17,273.60
Core resources built 13.1%: CAD 23,121.50 to 35,356.90
Security, gateway and connections 8.7%: CAD 15,355.50 to 23,481.30
Testing and fixes 1.4%: CAD 2,471.00 to 3,778.60
Docs, SDKs and load tests 4.3%: CAD 7,589.50 to 11,605.70
Royalties reconciled against a past period 8.7%: CAD 15,355.50 to 23,481.30
Launch 1.4%: CAD 2,471.00 to 3,778.60
Live cutover 2.1%: CAD 3,706.50 to 5,667.90
Hypercare 2.1%: CAD 3,706.50 to 5,667.90
Launch and first callers 5.3%: CAD 9,354.50 to 14,304.70
Holdback, 30 days after launch (10%): CAD 17,650 to 26,990

Start from this example

// questions

Questions we get about this.

Which POS systems can royalty reporting read from?

Those with a published API, which most current POS systems have. We check each of yours before we quote.

Can royalty rates differ by location or agreement?

Yes. Rates, minimums and fund contributions follow each agreement. Your agreements and your accountant set the rules; we give no tax advice.

What happens when a location's POS stops sending sales?

Head office gets an alert, and the location's statement is held until the sales arrive or someone enters them with a reason.

Back to the industry: Franchise businesses About the service: Integrations and automation

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call