Skip to main content

​
Netherlands Number & Sender Rules (ACM)

The Netherlands (NL) sits in Orbit’s regulated number-purchase set, so a Dutch DID order opens only after an approved compliance profile is attached. On the traffic side, Dutch marketing communications sit under the Telecommunications Act’s (Telecommunicatiewet) ePrivacy provisions and ACM (Autoriteit Consument & Markt) consumer enforcement, with the Bel-me-niet register as the national opt-out list. This page expands the NL row of the country-requirements matrix so you can assemble the profile before your first Dutch order and run Dutch traffic on a posture your counsel can review. The Netherlands is a tenant-owned burden. Orbit keeps the country-rules reference and the purchase gate; the legal posture is yours.
This page is documentation, not legal advice. ACM enforcement and the Dutch marketing-consent provisions apply against the sender, and the Bel-me-niet register is maintained outside Orbit. Have counsel review your consent capture and list hygiene; Orbit supplies the surfaces.

​
Where Orbit gates Dutch number purchases

NL is a member of the platform’s phone_number_purchase regulated set (DE, GB, FR, BR, MX, IN, JP, FI, NL, SE) — the same registry that drives the compliance-profile wizard. For a Dutch order the gate works like this:
1

Create the profile

POST /api/v1/compliance/compliance-profiles with country_code: "NL" and use_case: "phone_number_purchase". The wizard surfaces the Dutch packet: a required business registration certificate (business_doc) and proof of address (address_proof), plus an optional government-issued ID (id_proof). The ID is optional because the carrier’s compound requirement accepts either an identity document or the company registration; upload it when your registration extract alone is thin. The data fields are the business identity block (registered name, registration number, address, contact person, email, phone) plus website and the use-case description with sub-allocation disclosure.
2

Submit and wait for carrier review

Submission fans the bundle to the carrier for review, typically a few business days. Track status on the profile; the gate opens only on approved. See the KYC Profile Submission Runbook.
3

Order the number

Place the Dutch order with the approved profile attached (compliance_profile_id). Without an approved profile the order gate answers the same 422 as a missing profile (COMPLIANCE_PROFILE_REQUIRED / COMPLIANCE_PROFILE_NOT_APPROVED), and a number bought ahead of approval lands at pending_compliance. It cannot originate traffic until the profile is attached and the carrier confirms.
Three Dutch obligations drive the tenant-side configuration:

​
The NL country-rules row

Read the live row first; the snapshot here is orientation:
registration: none means no statutory alphanumeric sender registry; carrier relabeling of unregistered senders is still a deliverability posture, so register the sender where identity stability matters.

​
Worked phone_number_purchase profile for NL

Attach the uploaded trade-register extract as business_doc and a recent utility bill as address_proof; add the signatory’s passport as the optional id_proof if the carrier asks for the identity branch of its compound requirement. Then attach the approved profile at order time exactly as the KYC runbook shows.