How Coding the Curbs (Amsterdam) Kept Scaling Up Its Fleximodo Parking Sensor Deployment — From an Express Top-Up to a 3.7x Production Order

Deployment Snapshot (Cumulative)

---

Order / Deployment Timeline

Note on earlier history: both orders reference a customer-support credit prepaid on an earlier invoice (2025070) that precedes the September top-up. This confirms Coding the Curbs' relationship with Fleximodo was already established before Order 1 in this record, though the details of that earlier engagement fall outside the scope of these two invoices and are not restated here as a numbered order.

---

The Client

Coding the Curbs is a Dutch kerbside-management and smart parking specialist based at Johan Huizingalaan 763A, in Amsterdam's Slotervaart district. The company name is an unusually explicit statement of market positioning: the kerb — the narrow strip of urban pavement at the edge of the carriageway — is among the most contested and most valuable pieces of municipal real estate in most European cities, and coding it (turning it into data, measuring it, managing it, pricing it dynamically) is the frontier of contemporary urban mobility.

Amsterdam is one of the most actively managed kerbside environments in Europe, applying progressive policies on kerbside allocation, dynamic pricing, delivery windows, and mobility-hub integration. A Dutch company named Coding the Curbs is clearly positioned to work with municipalities and mobility operators pushing the frontier of kerbside digitalisation, and in-ground smart parking sensors are one of several technologies such a company integrates into a broader kerbside data infrastructure.

Why Amsterdam Kerbside Data Requires Precise, Rapidly-Deployed Sensors

Dutch kerbside management operates at a level of technical and policy sophistication that distinguishes it from most European smart parking markets. Amsterdam in particular has been progressively digitalising its kerbside infrastructure for over a decade, combining municipal policy (paid parking zones, residents-only blocks, time-of-day restrictions), commercial operator infrastructure (private car parks, hotel loading zones, event venues), and increasingly mobility-as-a-service integration (shared mobility hubs, micro-mobility docks, delivery operator zones). Companies working on Amsterdam kerbside deployments — including Coding the Curbs — build technology layers spanning multiple municipal and commercial stakeholders simultaneously.

For kerbside-data companies, sensor reliability matters in a particular way: the data feeds policy enforcement, dynamic pricing decisions, and sometimes real-time information to citizens. Any gap in sensor coverage or reliability directly affects downstream data quality, which affects everything built on top of it. Sensors that fail silently, report incorrectly, or need field intervention disrupt the pipeline and undermine end-user trust. The quality bar is high, and the margin for hardware variability is narrow. Spatial density compounds this: the more parking spaces a kerbside-data operator monitors, the more complete the occupancy picture becomes, and the more valuable that data is for dynamic pricing, enforcement, and mobility analytics. Growing the sensor count is therefore not incidental — it is a core lever of the business model.

The Growth Story: From a Small Top-Up to a Larger Production Order in 49 Days

Order 1 — September 2025: An Urgent, Express-Shipped Top-Up

Coding the Curbs' first documented order in this record is small by production-deployment standards, but its line items reveal the operational context. The shipment references an earlier invoice (2025070) for customer support — meaning the support relationship was already established and prepaid before this particular shipment — and the shipping line specifies express, insured carrier, the profile of a top-up order needed with urgency rather than a planned initial rollout.

The most common reasons for express-shipping top-ups are sensor failures in the field that need immediate replacement, site expansions approved on a tight timeline, or production milestones that require hardware before a specific date. Standard Fleximodo shipping to the Netherlands runs over ground or standard air freight — reliable, cost-effective, and adequate for most planned deployments. Express insured shipping costs more per kilogram but arrives faster and carries explicit carrier insurance against loss or damage in transit. Coding the Curbs chose this option, meaning the hardware's timely arrival was worth the shipping premium. The underlying operational trigger is not stated in the invoice, but the pattern — an active, live deployment needing a fast patch — is unambiguous.

Top-up orders with express shipping are one of the less glamorous but most operationally telling patterns in a vendor's order history. They mark the point where a deployment has already passed through evaluation, commissioning, and field operation, and has reached the stage where real-world operational events are driving additional hardware requirements: a damaged sensor needing replacement, a section of kerbside added to the footprint after the original order, unexpected early end-of-life on a unit, or a city approving an expansion of a paid parking zone that now needs coverage. In every scenario, the common element is operational urgency that justifies paying the shipping premium for faster arrival. For Fleximodo, supporting express shipping is what makes it operationally usable for customers whose deployments are already live and whose cadence depends on fast top-up response times.

The forward-prepaid customer support tied to invoice 2025070 is a similarly telling detail: it documents that Coding the Curbs already held prepaid support credit from an earlier invoice — support that rolls forward across multiple sensor orders rather than being repurchased with each shipment. This kind of arrangement is characteristic of mature customer relationships, where the support tranche is sized to cover multiple deployment phases rather than a single one. For Fleximodo, it simplifies the commercial relationship (one support agreement covering many orders); for Coding the Curbs, it removes the friction of renegotiating support on every individual order.

Order 2 — November 2025: A Planned, 3.7x Production-Scale Order

Forty-nine days after the September top-up, Coding the Curbs placed a second order — same product specification, same 10-year Deutsche Telekom connectivity, same forward-prepaid support from invoice 2025070, but at roughly 3.7x the sensor quantity of the first order. The 49-day gap sits in the fast category for repeat orders generally, consistent with a customer in active deployment ramp. But the character of the two orders differs sharply: the first was reactive (express shipping, suggesting urgency); the second is proactive (standard shipping, larger planned quantity, suggesting deliberate expansion).

This pattern — a small reactive order followed quickly by a larger planned order — is common where the first order reveals that existing sensor count is insufficient, prompting the customer to expand coverage area rather than simply replace or supplement individual units. For Coding the Curbs, expanding sensor coverage is a core business driver: the value of kerbside data increases with spatial density, and moving from a handful of top-up sensors to a meaningfully larger batch is the pattern of a company actively building its kerbside data coverage toward a commercially useful density threshold.

The specification held identical between the two orders — itself a signal. Coding the Curbs validated the product and the connectivity profile on the first order and scaled without needing to change anything about the configuration. For a technology vendor, the best possible second-order signal is a repeat specification at larger scale: it means the NB-IoT parking sensor worked exactly as specified, and the customer wants more of the same.

Reading the Two Orders Together

22 September 2025: Order 1. Express insured top-up, small batch, operational urgency, reactive.

10 November 2025: Order 2. Planned production batch at 3.7x scale, standard shipping, proactive.

Cumulative across 49 days: Two orders confirming an accelerating Amsterdam deployment, with a support agreement (invoice 2025070) that predates both and rolls forward across each.

The trajectory from reactive top-up to planned production order in under seven weeks demonstrates an accelerating engagement. Coding the Curbs is not merely maintaining an existing deployment — it is expanding its Amsterdam kerbside sensor footprint at a pace suggesting either new deployment sites coming online, or existing sites being densified to reach the spatial coverage its kerbside-data business model requires.

Fleximodo NB-IoT Sensor Standard With 10-Year Deutsche Telekom Connectivity: Technical Profile

Specification	Detail
Sensor model	IoT Parking Sensor Standard (NB-IoT, in-ground)
Detection technology	Dual detection — magnetometer combined with radar
Detection accuracy	99.96%
Dimensions	115 mm diameter, height 64 mm
Weight	390 g
Battery lifetime	6 years operational (10-year rated battery life across the Fleximodo sensor range)
Ingress protection	IP68
Impact resistance	IK10
Connectivity	NB-IoT — Deutsche Telekom, 10-year bundled SIM, delivered via a GOSPACE LABS-managed private APN
Customer support	Forward-prepaid via invoice 2025070; rolls forward across both the September and November orders
Shipping (Order 1, Sep 2025)	Express, insured carrier, to the Netherlands
Shipping (Order 2, Nov 2025)	Standard, to the Netherlands
Warranty	1 year standard

This in-ground parking sensor's 99.96% detection accuracy is maintained year-round — canal-side damp winters through summer heat — through automatic temperature compensation: the sensor's firmware continuously recalibrates its magnetometer baseline as ambient temperature shifts through Amsterdam's seasons, so the dual detection technology (magnetometer plus radar) doesn't mistake thermal drift for a vehicle arriving or leaving. For a live kerbside deployment where every sensor's reading feeds directly into enforcement and pricing decisions, that consistency is what makes both a fast top-up order and a 3.7x scale-up low-risk ways to grow coverage rather than introducing new data-quality uncertainty.

The Deutsche Telekom NB-IoT connectivity runs on a dedicated, GOSPACE LABS-managed private APN rather than a generic consumer SIM profile, keeping sensor traffic isolated from the open internet and simplifying long-term fleet management as Coding the Curbs' Amsterdam sensor count grows. Deutsche Telekom's NB-IoT footprint has strong coverage in the Netherlands via KPN roaming agreements and direct Deutsche Telekom subsidiary relationships, and the 10-year bundle eliminates recurring SIM management over the full operational decade — fixing connectivity cost upfront and removing a planning variable for a kerbside-data company whose operational model depends on reliable long-term sensor connectivity.

---

Fleximodo smart parking technology is deployed in 30+ countries. View all products | See Geosparc's seventh Belgian DOTA-enabled order | See Xerovex's Maastricht multi-product demo kit

---

Frequently Asked Questions

Why did Coding the Curbs keep scaling up its Fleximodo deployment? Coding the Curbs' first documented order was a small, express-shipped top-up addressing an urgent gap on an already-live Amsterdam deployment. Once that specification proved out in the field, the company placed a second, planned order 49 days later at roughly 3.7x the quantity — standard shipping, same spec, no reconfiguration. That trajectory (reactive top-up followed quickly by proactive scale-up) is consistent with a kerbside-data business whose value grows with spatial sensor density: validating the hardware on a small batch and then expanding coverage toward a commercially useful density threshold.

Why does a customer choose express insured shipping for smart parking sensors? Express insured shipping costs more per kilogram but arrives faster and carries explicit carrier insurance. Customers choose this option when operational urgency justifies the premium: replacing damaged sensors in a live deployment, completing site expansions with tight deadlines, or responding to real-world events that require hardware before a specific date. It's the profile of top-up orders on active deployments — as seen in Coding the Curbs' September 2025 order.

What does a 3.7x scale-up in 49 days signal? It signals that the first order validated the product and the customer is expanding coverage at pace. The shift from a small reactive top-up (express shipping) to a larger planned production order (standard shipping) indicates a transition from maintenance mode to active expansion of the sensor footprint — exactly the pattern in Coding the Curbs' November 2025 order.

Why is spatial density important for kerbside-data companies? Kerbside data value increases with spatial density — the more parking spaces monitored, the more complete the occupancy picture, and the more valuable the data for dynamic pricing, enforcement, and mobility analytics. Expanding sensor coverage builds toward a commercially useful density threshold where the data becomes actionable at scale.

How does forward-prepaid customer support work across multiple orders? Forward-prepaid support is purchased in a larger tranche that covers multiple subsequent orders. Later invoices reference the earlier prepaid agreement rather than purchasing new support with each shipment. Coding the Curbs' support, prepaid via invoice 2025070, rolled forward to cover both the September top-up and the November scale-up — simplifying the commercial relationship for both vendor and customer and reflecting a mature, ongoing collaboration.

Why is 10-year Deutsche Telekom connectivity well-suited to Dutch kerbside-data deployments? Deutsche Telekom NB-IoT has strong Netherlands coverage via KPN roaming agreements and direct subsidiary relationships, delivered here over a GOSPACE LABS-managed private APN. The 10-year bundle eliminates recurring SIM management over the full operational decade, fixing connectivity cost upfront. For kerbside-data companies whose operational models depend on reliable long-term sensor connectivity, fixed long-term costs remove a major planning variable — a benefit that compounds as the sensor fleet scales up.

What is automatic temperature compensation, and why does it matter for a scaling deployment? Automatic temperature compensation is a firmware process that keeps a magnetometer parking sensor's occupancy readings accurate as ambient temperature changes. It prevents heat- or cold-driven drift in the magnetic-field reading from being misread as a vehicle event, helping Fleximodo's in-ground parking sensors sustain 99.96% detection accuracy through Amsterdam's full seasonal range. That stability matters directly to a kerbside-data company scaling up sensor count, since data quality has to hold as coverage grows.

---