Unicom Americas Mobile Business
English
Customer Portal Portal Request a quote
Unicom Americas Mobile Business
Request a quote Customer Portal

E-commerce & marketplaces: A2P SMS and mobile data

Order and delivery SMS on registered senders.

Unicom Americas – Mobile Business team

Request a quote

In figures

  • Order and delivery messages are transactional: they can reach a recipient who never opted in to marketing, but the sender still needs registration where the destination requires it.
  • GSM-7 fits 160 characters in one segment; Chinese or Arabic text switches to UCS-2 at 70 characters, and an emoji costs two of those, so the same text can cost several times more segments.
  • A delivery receipt reports what the network observed, not what the handset displayed; reconciliation belongs at order level, with message IDs kept alongside the order.
  • Checkout verification and order updates are different traffic classes: one is a login secret with a short lifetime, the other a notification that can be retried and batched.
  • Throughput per bind is reserved before a peak event, and templates are tested against local filters first.

This page is not legal advice.

Scenarios

Order and delivery messaging

An order confirmation, a dispatch notice and a delivery-window message are three separate templates with three different failure costs. Keep them short enough to stay in one GSM-7 segment, avoid public URL shorteners that local filters block, and give every message a purpose the recipient can recognize. Register the sender before the first send, because a route that works in testing can be filtered on launch day. Reconcile delivery receipts against orders and refunds, not against raw message counts: a late delivery notice and a missing one look the same in a dashboard total.

Checkout verification and account security

A checkout OTP is a short-lived secret, so its design is about time and retries: set a validity window, cap resends, rate-limit by number and device, and fall back to an alternative channel when the code does not arrive. Message text should not carry a full account number or a link to a login page, because the message may be forwarded. The OTP fraud explainer covers the patterns.

Rider fleets

Delivery riders are tracked as a two-wheeler fleet, not as phone users: position, battery and delivery state travel on a data profile, while the rider's handset talks to the platform app over whatever network it has. Shift handovers, depot geofences and battery-swap stops are the events that generate traffic. Vehicle connectivity, including e-bikes and shared fleets, is covered on the smart mobility page; this page covers the buyer-facing messaging that sits around it. The data profile is sized per vehicle, so a rider who leaves the company does not leave a live line behind.

Returns, pickup and locker codes

A return label and a pickup code are one-time secrets with a place and a deadline attached. Send the code in the same message as the location and the window, keep the wording stable so recipients recognize it, and expire it server-side rather than trusting the message. Lockers add a second channel: the locker sends an event when a parcel is deposited, and the buyer gets a code that opens one door once. Two-way replies help here, but they need a number that can receive messages, not an alphanumeric sender ID, which is normally one-way.

HQ-to-China links

Marketplaces moving goods and data between headquarters and China run two legs: the commercial traffic between teams and suppliers, and the data path behind sourcing, inventory and finance systems. Both start with naming the applications, the sites and the direction of the traffic, because a link sized for office email behaves nothing like one carrying order data. ICP filing and cross-border data-transfer steps apply to some designs; scope them with counsel alongside the contract, and treat the connectivity choice as separate from the filing question. The China compliance page lists the questions to put to counsel. This is not legal advice.

Product bundle

FAQ

Do you send on our behalf or as our platform?
Either. Platforms send as CPaaS with their own throughput; enterprises send direct. Tell us which you are and we assess the fittest access, because the sender registration and the contract sit on different sides of that line.

How do rider phones connect?
Riders run on fleet data profiles; the two-wheeler detail lives on the smart mobility page. The buyer-facing messages that tell a customer where the rider is travel on a separate A2P route with its own sender registration.

What about our China sourcing offices?
HQ-to-China links are scoped with filing and data-transfer steps alongside the messaging contract. Name the applications and the sites first; the compliance questions follow from that inventory, not from the contract.

Why do order messages fail at launch?
Usually one of three reasons: the sender was never registered for that destination, the template trips a local link or keyword filter, or the route was sized for testing rather than for launch volume. Pre-test the template, register early and reserve throughput before the campaign calendar starts.

How do we prepare for a peak sales event?
Forecast the burst per destination, reserve the throughput, and pre-test the templates that will change. Keep a queue with a retry policy and a defined expiry, so a backlog does not turn into thousands of stale delivery notices after the event.

Sources

  1. 3GPP TS 23.040: SMS technical realization
  2. MIIT Circular [2017] No. 32 (via CAC): cross-border lines

Request a quote

Tell us whether you send as a platform or as the enterprise itself; we assess the fittest access.

Request a quote Enterprise