Skip to main content

​
Buy, bulk, and orders

Buying numbers in Devotel Orbit happens under Numbers → Buy in the dashboard, on three tabs: Buy (one number at a time), Bulk (a criteria-based batch), and Orders (the history of every bulk purchase). This page maps each surface to its job, walks a purchase from search to provisioned number, and lists what to wire up before a new number takes traffic. For the endpoint-by-endpoint API recipe see Buy and provision numbers. For what a number can do once it is in your inventory, see Phone numbers overview.

​
Where the three buy paths live

The single wizard and the bulk form draw from the same live inventory and charge the same wallet; they differ in shape, not in source. Orders is the read-only ledger that every bulk purchase writes to; single purchases land directly in your inventory.

​
Single-number buy

  1. Pick a country. The country picker drives everything below it: capability pills on each result are pre-dimmed to what that country actually supports, so you never order voice on a market that only sells SMS. The per-market matrix lives in Country capabilities.
  2. Search. Each search queries live inventory; results are not cached, so availability and monthly cost are current at search time. The flip side is turnover: a number another customer holds can disappear between search and checkout. Area-code and pattern filters narrow the same live result set.
  3. Regulatory preview gate. For regulated ranges the preview lists the identity fields and documents the carrier requires before the number can activate. If the market requires an approved compliance profile and none is attached to your organization, checkout stops and sends you to the compliance wizard under Settings → Compliance; the purchase completes once a profile is approved. What the preview checks is covered in Regulatory preview.
  4. Check out. The purchase provisions through your active DID provider. Only lines that succeed are charged; a failed checkout never debits your wallet.
  5. Watch the provisioning state. After checkout the row shows Pending while the carrier provisions, then either lands in your inventory at Numbers or fails with a reason. If the number vanished between search and checkout, run a fresh search rather than retrying the stale row.

​
Bulk buy

Bulk submits a criteria-based batch (country, capabilities, quantity or pattern) in one call, up to 50 numbers per order. To hold a larger block of matching inventory while you decide, use the reserve flow instead: Bulk reserve holds up to 1000 matching numbers for 15 minutes, then finalizes or cancels the block. Expect partial success on large batches and plan for it:
  • Aggregate outcome. Every bulk order resolves to delivered (every line succeeded), partial (some lines succeeded, some failed), or failed (no line succeeded). partial is a normal result on big batches, not an error state.
  • Per-line reasons. Each failed line carries a carrier error code. NUMBER_NO_LONGER_AVAILABLE means inventory turnover: someone bought that number first, and the fix is a fresh search, not a retry of the stale row. A regulatory code means the market needs an approved compliance profile before those ranges can provision.
  • Billing. Failed lines are never charged. The order records the full batch total and the amount actually debited, so finance can see both in one place.
  • Rate limit. Bulk creation is limited to 2 submissions per minute per tenant because one call fans out to many carrier requests. Order reads carry no such limit; poll on whatever cadence reconciliation needs.
Every bulk submission persists an order record the moment it is created, so the batch is auditable even if you close the tab: that record is what the Orders tab and Bulk order history read from.

​
Order status page

Numbers → Buy → Orders lists every bulk purchase, newest first, with requested, delivered, and failed counts and the aggregate status. Open a row to expand the per-line breakdown: E.164 number, country, capabilities, monthly cost, and the line’s own status.
  • Delivered on a line means the number is in your inventory and ready to wire up (below).
  • Pending means the carrier is still provisioning; give it time before treating the line as stuck.
  • Failed shows the carrier error code for that line, which tells you whether the remedy is a fresh search (turnover) or a compliance profile (regulatory hold).
Read the aggregate first, then the lines: partial with turnover errors is routine churn; partial or failed with regulatory errors across a whole market means the batch needs a compliance profile before any retry will land. When a batch needs line-by-line retry and reconciliation, follow the Bulk order recovery runbook. If a number you expected never appears in inventory at all, Number backorder & waitlist covers the out-of-stock path. The ledger is append-only and read-only for every role that can see it; nothing on the page mutates an order, and it records inbound provisioning only, never outbound routing.

​
Who can buy, who can approve

  • Read — searching inventory, opening number detail, and reading the Orders ledger are available to every seat that can open Numbers. API reads require the numbers:read scope.
  • Buy — single and bulk purchases spend from the organization wallet and require numbers:write: owner, admin, and developer seats. Viewer and billing seats can see Numbers but cannot initiate a purchase; the billing seat’s surface is invoices and usage, not buying.
  • Approve — there is no separate purchase-approval step. The gate is regulatory: ranges in regulated markets require an approved compliance profile, which owner and admin manage under Settings → Compliance. Until a profile is attached, checkout for those ranges blocks for every seat, owner included.
  • Audit — because orders are append-only, the Orders tab doubles as the purchase audit trail for finance; reconcile it against usage exports as described in Bulk order history.

​
Post-purchase wiring checklist

A delivered number is provisioned but not yet routed. Before it takes traffic:
  1. Attach it to a messaging service if it will send SMS or WhatsApp, so outbound sends pick it up as an approved sender.
  2. Configure the inbound route from the number’s detail page: point voice and SMS inbound at the flow, agent, or endpoint that should receive traffic.
  3. Run the health check at Numbers → Health (or the number’s health panel) to confirm the routing entries exist and resolve; Number health explains each check, and Inbound resolution & health walks the repair loop when an entry is missing.
  4. Set lifecycle hygiene — renewal, expiry alerts, and what happens when a number is released — per Number lifecycle, so the number you just bought does not silently lapse.

​
See Also