Skip to main content

Confirm where the order should go

Alkax supports two delivery patterns: a person can share an existing Alkax place with a driver, or a merchant can request confirmation before dispatch through Delivery Intelligence.

An Alkax delivery flow from merchant order to a confirmed delivery destination.

Confirm the destination before dispatch so fulfilment works from a dependable place record rather than ambiguous free text.

Pattern 1: share an Alkax place​

This fits direct, person-to-person delivery:

  1. The recipient creates or selects their destination.
  2. They share the Alkax link, Plus Code, or QR code.
  3. The driver opens the place and starts navigation.
  4. The place description and arrival details help with the final approach.

Learn how address sharing works →

Pattern 2: confirm before dispatch​

This fits an e-commerce, courier, or merchant system:

  1. The merchant creates an address-confirmation request with its own order reference.
  2. Alkax emails the recipient a secure, time-limited link.
  3. The recipient keeps the proposed place, selects a different Alkax place, or creates a missing one.
  4. The recipient can add a private entrance photograph for moderation.
  5. Alkax freezes the confirmed destination as an immutable snapshot.
  6. The merchant retrieves the result or receives a signed webhook.
  7. The fulfilment team dispatches using the confirmed snapshot.

The recipient does not need an Alkax account to use the confirmation link.

What the merchant gains​

  • a canonical Alkax place when one is selected or created;
  • confirmed coordinates and human-readable arrival context;
  • explicit lifecycle states instead of an ambiguous free-text address;
  • confidence information when evaluation is available;
  • signed, retryable events for downstream order systems;
  • one merchant reference that can be reconciled with the order.

What remains private​

Recipient contact details, private delivery instructions, secure confirmation links, and delivery-only entrance media are not public place data. Entrance media is withheld until moderation approves it and is not exposed when rejected.

Start​

Integrate Delivery Intelligence →