Company onboarding
From paperwork to the first ride: what has to be in place before a company takes its first ride, how long each phase takes and what happens when something is missing.
Onboarding a company is not one click. Some things take days and depend on others — the bank, the tax office, the print shop, the app stores. That is why the order matters: the technical part takes one to three days, while paperwork and stores run in parallel for weeks.
Phases at a glance
| Phase | What happens | Duration | Who |
|---|---|---|---|
| 0 | Decisions: slug, legal name, bundle id, country, currency | 30 min | Company + platform |
| 1 | Legal minimum: tax id, bank account, fiscal certificate, terms and privacy | 5–15 working days | Company |
| 2 | Opening the company (done by the platform) | 15 min | Platform |
| 3 | “Ready to launch” gate — 12 checks | 1–2 h | Company owner |
| 4 | People, fleet, documents | 1–3 days | Dispatcher |
| 5 | Money: price list, zones, payment methods, fiscalisation | 1 day + external lead times | Owner |
| 6 | App branding | 2–4 h | Owner |
| 7 | App builds (Android, iOS) | 2–4 h first time | Platform |
| 8 | Google Play: account, listing, testing, release | 2–6 weeks | Company |
| 9 | Apple App Store — in parallel, same paperwork | 1–3 weeks | Company |
| 10 | Pilot and go-live | 1–2 weeks | Everyone |
Opening the company in the system
- Platform console → Companies → New company: slug, legal and display name, e-mail, tax id, country, plan, owner e-mail and name.
- The console shows the owner’s temporary password once. It is handed over through a secure channel, never by plain-text e-mail.
- The owner opens
/company/, signs in and must set a new password (at least 12 characters). - In Company profile they enter the address, contact and legal data; in Brand studio the brand name and colour.
This automatically grants the trial period from the plan, the core modules, the owner account with the OWNER role and an audit entry. For store releases the addon.store_launch_support module must be enabled — without it the Store release panel does not open, and only the owner can see it.
The “ready to launch” gate
While something is missing, opening a shift and creating a ride return 400 with the code errors.launchNotReady and a list of gaps. The gate is not bureaucracy — without a price list or an active driver a ride cannot be created correctly.
| # | Check | Means exactly | Filled in at | Blocks |
|---|---|---|---|---|
| 1 | companyProfile | legal name, address, city, e-mail | Company profile | yes |
| 2 | brand | brand name and colour | Brand studio | yes |
| 3 | legalDocs | terms and privacy filled in | Company profile | yes |
| 4 | serviceTypes | at least one service type | Pricing | yes |
| 5 | rates | every service type has a price list | Pricing | yes |
| 6 | paymentMethods | every service type has a payment method | Pricing | yes |
| 7 | zones | at least one zone | Zones | no (gate) |
| 8 | drivers | at least one active driver | Fleet | yes |
| 9 | vehicles | at least one activated vehicle | Fleet | yes |
| 10 | serviceArea | pickup radius | Company profile / Zones | yes |
| 11 | invoicing | at least one issuing channel enabled | Fiscalisation / Settlement | yes |
| 12 | fiscal | HR: certificate, tax id, premises and device, operator, production mode | Fiscalisation | yes, hard |
Brand and app builds
The brand is edited in the Brand studio (Company → Brand and apps). The wizard shows the real screens of both apps with the new colours before saving, and the name, colour, logo and tagline take effect immediately — without a new version, because the app fetches them on start.
App builds run through one script with a company profile stored outside the repository (Apple Team ID, keystore, Firebase, bundle ids):
# provjeri alate i ispiši sve nedostatke odjednom
node tools/build-apps.mjs --slug taxi-a --mode release --bundle --check
# Android (AAB za Play) i iOS (IPA za App Store)
node tools/build-apps.mjs --slug taxi-a --mode release --bundle
# brza probna gradnja za uređaj
node tools/build-apps.mjs --slug taxi-a --app driver --platform ios --mode debug
Artefacts land in dist/taxi-a/ and logs in build-logs/. Before building, the script checks Flutter, JDK 17, the Android SDK, the Firebase configuration, signing and the Apple Team, and prints all problems at once instead of stopping at the first.
App stores: what they actually require
- Google Play: the company opens the account (not the platform), with DUNS or tax-id data; the app goes through closed-channel testing before public release.
- Apple: same paperwork plus annual membership; review requires an explanation of background location (driver app) and the reason for location access.
- Store listing: icon, screenshots per size, description, category, privacy policy at a public address.
- After release: a version bump is needed only when app behaviour changes. Brand, prices and in-app content do not require a new release.
Checklist before the first ride
- The readiness gate is green (12/12), or the exception is recorded with an expiry date.
- The price list covers all service types, including fixed inter-zone prices where the company has them.
- At least one driver has an active shift, and the vehicle is activated with valid documents.
- Terms and privacy are published on the company’s address, and links work from both apps.
- A test ride went through the full loop: booking → assignment → pickup → completion → receipt.
- A fiscal receipt was issued in production mode and is visible in settlement.