Driveosplatform catalogue

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.

Phase 0 blocks everything elseThe company slug and the app bundle id are decided before the company is opened. The slug does not change later because it is part of the address, the app identity and deep links; changing it would mean a new app in the store.

Phases at a glance

PhaseWhat happensDurationWho
0Decisions: slug, legal name, bundle id, country, currency30 minCompany + platform
1Legal minimum: tax id, bank account, fiscal certificate, terms and privacy5–15 working daysCompany
2Opening the company (done by the platform)15 minPlatform
3“Ready to launch” gate — 12 checks1–2 hCompany owner
4People, fleet, documents1–3 daysDispatcher
5Money: price list, zones, payment methods, fiscalisation1 day + external lead timesOwner
6App branding2–4 hOwner
7App builds (Android, iOS)2–4 h first timePlatform
8Google Play: account, listing, testing, release2–6 weeksCompany
9Apple App Store — in parallel, same paperwork1–3 weeksCompany
10Pilot and go-live1–2 weeksEveryone

Opening the company in the system

  1. Platform console → Companies → New company: slug, legal and display name, e-mail, tax id, country, plan, owner e-mail and name.
  2. The console shows the owner’s temporary password once. It is handed over through a secure channel, never by plain-text e-mail.
  3. The owner opens /company/, signs in and must set a new password (at least 12 characters).
  4. 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.

#CheckMeans exactlyFilled in atBlocks
1companyProfilelegal name, address, city, e-mailCompany profileyes
2brandbrand name and colourBrand studioyes
3legalDocsterms and privacy filled inCompany profileyes
4serviceTypesat least one service typePricingyes
5ratesevery service type has a price listPricingyes
6paymentMethodsevery service type has a payment methodPricingyes
7zonesat least one zoneZonesno (gate)
8driversat least one active driverFleetyes
9vehiclesat least one activated vehicleFleetyes
10serviceAreapickup radiusCompany profile / Zonesyes
11invoicingat least one issuing channel enabledFiscalisation / Settlementyes
12fiscalHR: certificate, tax id, premises and device, operator, production modeFiscalisationyes, hard
An exception exists, but it is not the pathThe platform can temporarily release a company (“Force ready”) with a reason and an expiry date. When the date passes, the block returns by itself. It is meant for pilots and migrations, not for regular operation.

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):

bashgradnja obje aplikacije za tvrtku DEMO-TAXI
# 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.
The most common rejection reasonAn app that asks for a permission without an explanation in the interface itself (always-on location, notifications, camera). Every permission has company-language text and an explanation at the moment of the request.

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.