Delivery zones, drawn on a map.
Fees that price themselves.
A map-based delivery zone system for Printout: admins draw zones directly on Google Maps, set a fixed fee or a per-kilometer rate for each zone, and customers get the right delivery fee automatically — from a pin they drop on the map at checkout, on both the website and the mobile app.
From a fixed area list to real geographic zones.
Today, Printout's delivery fees come from a manual list of named areas, each with one flat fee, chosen by the customer from a dropdown. That works — until a customer picks the wrong area, a new district needs coverage, or pricing needs to reflect real distance. This engagement replaces the list with true geographic zones: the admin draws each zone's boundary on Google Maps, chooses how it's priced, and the system resolves every order's delivery fee automatically from the customer's exact location.
Draw zones, don't type them
Admins create and edit delivery zones by drawing boundaries directly on a Google Map in the dashboard — and see all zones together on one map.
Price each zone its own way
Every zone is either a fixed delivery fee or a per-kilometer rate. Per-km zones can measure straight-line or real Google driving distance — the admin picks.
Never lose an out-of-zone customer
Orders outside all zones either get a default fallback fee or are politely blocked — with a coverage-request form so Printout learns exactly where demand is coming from.
Built like a product, not a project.
Three things separate us from a traditional agency engagement: tight scope, weekly delivery, and a single team that owns the whole journey.
Scoped tightly
Every engagement starts with a written alignment doc. No ambiguity on what's in, what's out, or what 'done' looks like.
Shipped weekly
Every Friday ends with something you can review live on a staging URL, not in a slide deck.
One team, end-to-end
Strategy, design, and engineering in one room. No hand-off tax, no agency telephone game.
What this engagement covers.
Seven modules, delivered end-to-end across the backend, admin dashboard, website, and mobile app.
Zone management on Google Maps
A new Zones section in the admin dashboard. Admins draw each zone's boundary as a polygon on Google Maps, name it, color it, and activate or pause it. A master map view shows every zone at once, so coverage and gaps are visible at a glance.
Zone pricing engine
Each zone carries its own pricing mode: a fixed delivery fee, or a per-kilometer rate multiplied by the distance from Printout's pickup point to the customer. Per-km zones can measure straight-line distance or actual Google driving distance — configurable per zone, with an optional minimum fee.
Out-of-zone handling
An admin setting decides what happens outside all drawn zones: apply a configurable default delivery fee, or block delivery and show a 'we don't deliver there yet' message with a coverage-request form. Requests are captured with the customer's location and contact details and listed in the dashboard — so new zones are opened where demand actually is.
Customer map pin — website
The website address flow gains a Google Map pin step: the customer drops a pin (with search and auto-locate), and the address is saved with exact coordinates. The delivery fee for their zone appears live in the cart and at checkout before they pay.
Customer map pin — mobile app
The same experience in the Flutter app: a native map pin picker in the address and checkout flow, live delivery fee calculation, and the same out-of-zone messaging — consistent across web and mobile.
Automatic fee resolution at checkout
The backend resolves which zone the customer's pin falls inside and computes the delivery fee automatically — no more manual area selection, no wrong-area fees. The resolved zone and fee are stored on every order, and existing areas/fees keep working during the transition.
Testing, deployment & project management
End-to-end testing across all four platforms, staged rollout (staging → production), app store release of the updated mobile app, and coordination throughout the engagement.
How we work together.
Tight, accountable cycles. Every week ends with something live, not a slide.
Discovery & alignment
Kickoff call, confirmation of zone pricing rules and pickup points, Google Maps API setup on Printout's account, and a written alignment document.
Build the engine
Backend zones, pricing engine, and admin map-drawing UI first — so zones can be configured and verified with real addresses before customer surfaces change.
Ship the customer experience
Map pin and live fee display on the website and mobile app, wired to the new engine, reviewed weekly on staging.
Verify & release
End-to-end tests with real zone shapes and edge cases (zone borders, overlaps, out-of-zone), UAT sign-off, then production rollout and app release.
Three to four weeks. Engine first.
Indicative timeline pending kickoff confirmation. The backend engine and admin map tools land first, then the customer-facing surfaces, then verification and release.
Backend zones & pricing engine
Admin dashboard — zones on the map
Website & mobile app
Testing, UAT & release
{{PAYMENT_TERMS_LINE}}
Two ways to get it.
One simple decision.
The delivery zones module can be included in Printout's monthly maintenance plan as part of the feature roadmap, or taken as a standalone one-time add-on. Same scope and delivery either way.
Budget Summary
- ✓ Delivery zones delivered as part of the feature roadmap
- ✓ No separate invoice — covered by the monthly hours
- ✓ Ongoing maintenance of the feature included afterwards
- ✓ Full plan benefits: bug fixes, backups, security, support
- ✓ Minimum 3-month engagement · monthly payment at the beginning of each month
Option B — One-Time Add-on
What's included.
What's not.
Both options cover all design, development, testing, and deployment. Third-party usage costs — primarily Google Maps — run on Printout's own accounts and are excluded, detailed below so there are no surprises.
End-to-End Delivery
- ✓ Backend zone & pricing engine with APIs
- ✓ Admin map drawing and zone management UI
- ✓ Website and mobile app map pin flows
- ✓ Out-of-zone handling and coverage requests
- ✓ Google Maps API setup and integration
- ✓ Testing, UAT, staged production rollout
- ✓ Mobile app store release of the update
Not Covered
- ✗ Google Maps API usage fees (billed by Google)
- ✗ Server/hosting infrastructure costs
- ✗ App Store / Play Store developer fees
- ✗ New modules beyond the scope above
- ✗ Major changes requested after approval
Google Maps Usage Fees
Map display, place search, and driving-distance calculations use Google Maps Platform APIs on Printout's own Google Cloud account. Google includes a monthly free usage credit that typically covers small-to-medium volumes; usage beyond it is billed by Google directly. We configure the APIs, restrict the keys, and recommend settings that keep usage — and cost — as low as possible. Straight-line distance mode uses no Google API at all.
Full ownership. No lock-in. No licensing fees.
On final delivery you receive full ownership of all source code, infrastructure setup, and documentation produced during this engagement. Unrestricted rights to operate, modify, and scale. The Mok Company retains no claim over deliverables. Source code is delivered via private repository transfer or archive upon final payment.
Companies that
chose The Mok Company.
A growing portfolio of brands across energy, hospitality, travel, automotive, retail, and real estate — all delivered under one roof.
Our masterpieces live in production.
A snapshot of platforms shipped under The Mok Company across enterprise, e-commerce, real estate, energy, and hospitality.

Taggz

Lexus Yemen

Hino Yemen

Atta Sons

Futura Energy
Turbo Compression

Printout Solutions

Triangle Heavy Equipment
Ready to start.
Five steps from where we are today to Week 1 kicking off.
Where innovation
meets execution.
The Mok Company is a multidisciplinary business and technology consultancy dedicated to empowering organisations through tailored strategy, intelligent systems, and scalable solutions — from concept to creation. Let's put Printout's delivery on the map.


















