Skip to main content
Talk to an expert
what3words logo

what3words integration for ecommerce fulfilment

Precise delivery locations encoded into every despatch instruction what3words translates customer addresses into memorable three-word location codes, eliminating postcode ambiguity and reducing delivery exceptions at the last mile. Codes flow into your WMS and 3PL systems, and back to customers via tracking notifications. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: shipping connector, warehouse integration, fulfilment plugin, app.

what3wordsiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a what3words integration gives you.

Fewer failed delivery attempts

Drivers and recipients no longer rely on ambiguous postcodes or incomplete street addresses; the three-word code pinpoints the exact drop-off, reducing misdeliveries and repeat attempts.

Cleaner despatch instructions

WMS and 3PL systems receive unambiguous location codes alongside order line items; despatch teams can pass codes directly to drivers and customers without interpretation.

Reduced customer contact for address clarification

Customers see their three-word address code at checkout and can refine it themselves if needed; despatch teams no longer field calls to confirm 'which building' or 'which entrance'.

Simplified logistics for complex locations

Businesses serving industrial parks, apartment complexes, multi-unit buildings or rural addresses benefit from precise location data; carriers can navigate and confirm drop-off points without ambiguity.

02 · When it's worth it

Where a what3words integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Encode customer delivery addresses as three-word codes during order checkout or post-capture
Pass precise location data to WMS and 3PL systems for accurate despatch instructions
Reduce carrier misdeliveries and failed delivery attempts by removing postcode ambiguity
Enable customer self-service location refinement at checkout for complex or unmarked addresses
Surface what3words codes in despatch confirmations and tracking notifications sent to customers
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

No conditional encoding rules by carrier or destination

what3words API encodes every address uniformly; commerce owners cannot define rules to encode only addresses above a threshold distance, or to skip encoding for addresses already precise, or to apply carrier-specific encoding logic.

Limited integration with WMS pick-and-pack workflows

what3words codes flow into despatch systems but do not directly influence WMS picking, packing or staging logic; teams must manually reference codes in their warehouse execution software.

No built-in fallback for API downtime or rate limits

If what3words API is unreachable or rate-limited, orders cannot be encoded; commerce and despatch teams must decide whether to hold orders, proceed without codes, or manually intervene per delivery.

Address data quality and coordinate accuracy required

Encoding relies on accurate postcode or latitude/longitude; if commerce order capture collects incomplete or misspelled addresses, the what3words API may return unexpected results or fail to encode.

No native multi-language address or code presentation

Three-word codes are language-agnostic, but customer notifications and driver instructions require commerce or WMS teams to integrate translation and presentation logic for local delivery markets.

04 · The real work

Despatch failures cluster at the address level: postcode ambiguity, unmarked buildings and incomplete street names account for a rising share of failed attempts as delivery density increases and urban addresses become more complex.

05 · Where it sits

Where this integration sits in your estate.

what3words holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Platform-agnostic by design. what3words sits at the centre of your estate, not at the edge of one platform.

System of record
Source / owner
what3words
Location data transformer for last-mile despatch accuracy
  • Three-word location code generation and validation
  • API integration with what3words service
  • Timeout, retry and fallback logic
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Customer address capture and validation
  • Despatch instruction and location rules
  • Customer notification templates and tracking display
Connected neighbours
Integration layer
WMS or 3PL
Receives encoded location codes in despatch payloads; passes back despatch and tracking events for customer notifications.
Integration layer
ERP
Provides order and address data to commerce; receives despatch confirmations and delivery exceptions for accounting and stock reconciliation.
Integration layer
Customer notification service
Renders and sends tracking emails and SMS; iWeb injects three-word codes into message templates.
Integration layer
Carrier routing system
Receives codes as part of despatch instructions; may or may not consume them depending on carrier capability.
Integration layer
Map and geolocation service
Provides coordinate lookup and what3words map picker for customer address refinement at checkout.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • WMS (in-house or cloud)
  • 3PL and fulfillment provider
  • Carrier and routing systems
  • ERP (for address and order data)
  • Customer notification and tracking system
  • Maps and geolocation service
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into WMS/3PL & COMMERCE & CUSTOMER
←From COMMERCE
↔BOTH WAYS
Order location encoding: Commerce order capture includes customer delivery address; integration calls what3words API to convert postcode or coordinates into three-word code and passes the result downstream to WMS or 3PL dispatch system.
Address and coordinate extraction: Order data from commerce platform (including postcode, address line 1-2, or customer-provided coordinates) flows to the what3words connector for encoding before reaching warehouse execution.
Despatch confirmation with location code: WMS or 3PL sends back despatch event including the three-word code assigned to the drop-off; integration updates order or shipment record in commerce platform for customer visibility.
Customer self-service location refinement: At checkout or post-order, customer views their three-word code and can adjust it via what3words map interface; refined code flows back to commerce and downstream to despatch systems.
Notification and tracking: Despatch confirmation and tracking notifications sent to customer include the three-word address code, enabling driver and recipient to confirm exact location.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    API orchestration and timeout handling

    We build robust what3words API calls with configurable timeouts, retries and graceful fallback; if encoding fails, orders proceed through despatch workflows with manual location review flagged to handlers.

  2. 02
    Address data enrichment and validation

    We help standardise incoming address data (postcode format, coordinates) and validate it before encoding; we identify missing or malformed fields and route them to exception queues rather than failing silently.

  3. 03
    WMS and 3PL connector integration

    We embed three-word codes into despatch payloads sent to your WMS or 3PL; we map the codes into the fields your carrier system expects (delivery instructions, location reference, navigation data).

  4. 04
    Customer notification and tracking updates

    We ensure despatch confirmations, tracking pages and SMS/email notifications sent to customers include the three-word code; we handle template rendering, localisation and multi-channel delivery.

  5. 05
    Observability and exception handling

    We instrument the encoding pipeline with logging, metrics and alerting; we surface encoding failures, API rate-limit events and delivery address anomalies to your operations team in real time.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataDespatch instructions and location encoding rules
Source / ownerWMS or 3PL
Maintained byDespatch operations and WMS team
Noteswhat3words acts as a location data transformer; the WMS owns the final despatch instruction format and logic for when encoding is applied.
DataCustomer delivery address and coordinate capture
Source / ownerCommerce platform
Maintained byCommerce operations and checkout team
NotesCommerce platform collects and validates address at order time; what3words integration consumes this data and returns encoded location codes.
DataThree-word location codes
Source / ownerwhat3words API (read-only to commerce and WMS)
Maintained bywhat3words service
NotesCodes are generated on-demand by what3words; integration caches or stores codes in commerce and WMS systems for reference in despatch, tracking and customer notifications.
DataDespatch confirmation and tracking updates
Source / ownerWMS or 3PL
Maintained byWarehouse and carrier systems
NotesDespatch events include the three-word code for reference; integration propagates codes back to commerce platform for customer visibility in order status and tracking pages.
DataCustomer notification templates and messaging
Source / ownerCommerce platform or marketing/CRM system
Maintained byCommerce and customer experience teams
NotesTemplates determine whether and how three-word codes are presented to customers; integration injects codes into outbound messages (SMS, email, tracking page) at render time.
DataEncoding exception handling and fallback logic
Source / ownerIntegration configuration
Maintained byIntegration team and operations governance
NotesRules for timeout, retry, fallback, and manual review are owned by integration team; despatch team executes the rules when API or address data fails.
10 · Experienced integrator

Built this before

iWeb has integrated what3words into WMS and 3PL workflows for retailers, e-grocery and parcel carriers. We understand how location encoding sits between order capture and last-mile despatch, and how to handle API downtime, address validation and carrier compatibility without blocking fulfillment.

We design encoding strategies that balance API cost, customer experience and carrier system constraints.
We build fallback logic so that orders despatch even when what3words API is unreachable, and exception queues surface problematic addresses for manual review.
We integrate three-word codes into WMS despatch instructions, carrier payloads and customer notifications without breaking existing despatch rules or workflows.
We help you observe encoding success rate, latency and API rate limits, and alert your operations team when encoding drifts or fails at scale.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Validate that encoding succeeds for all address formats in your order database (postcode alone, postcode + unit, coordinates, free-text).
Confirm that encoded codes flow into your WMS despatch payload in the expected field and format for your carrier system.
Test API timeout and rate-limit fallback: verify that orders proceed to despatch (with manual flag) when encoding takes >5s or API returns 429.
Verify that despatch confirmations including three-word codes reach customers via email and tracking page, and that codes are clearly labeled.
Confirm that address validation catches malformed postcodes and missing unit numbers before encoding is attempted, routing them to exception review.
Load-test the encoding pipeline at your peak order rate to confirm API calls and response times do not cause despatch delays.
Test code reuse: verify that the same postcode encoded twice returns the same code and does not trigger duplicate API calls.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

API downtime blocks despatch workflow

If what3words API becomes unavailable mid-shift, commerce and WMS systems may halt order processing or queue orders indefinitely; teams must decide rapidly whether to skip encoding, use cached codes, or hold orders until service returns.

Stale or incorrect address encoding

If customer address data in commerce is outdated (old postcode, wrong unit number, moved to new building), what3words encodes the wrong location; driver navigates to the wrong place and delivery fails silently.

Encoding rules drift across teams

Despatch team and commerce team may encode addresses differently (one uses postcode, one uses coordinates); codes diverge, and WMS receives conflicting instructions or duplicate codes for the same delivery.

Carrier system rejects or ignores codes

Some carriers and routing engines do not consume three-word codes; codes are passed downstream but ignored by driver app or routing software, negating the benefit of encoding.

Customer confusion or distrust of novel location format

Customers unfamiliar with three-word codes may distrust the format or ignore it in notifications; if code differs from their remembered address, they may think the delivery is going to the wrong place.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about what3words integrations.

When should we encode an address as a three-word code - at order capture, or when the order reaches the WMS?

Encoding at order capture lets customers see and refine their three-word code before checkout; encoding at WMS dispatch reduces API calls and lets you skip encoding for local deliveries or pre-encoded addresses. iWeb helps you decide based on your carrier requirements, API budget and customer experience goals.

What happens if the what3words API is down or rate-limited during a surge?

iWeb builds fallback paths: orders can proceed without codes (flagged for manual review), cached codes can be reused for repeat customers, or queued for encoding when service returns. We help you define the fallback strategy and monitor which orders are affected.

How do we ensure the three-word code matches the actual delivery address the customer entered?

iWeb validates address data before encoding (postcode format, unit/building presence, coordinate accuracy). If validation fails, the order is routed to an exception queue for manual address review before encoding is attempted.

Do all our carriers accept and use three-word codes in their routing and driver apps?

Not all carriers integrate with what3words natively. iWeb helps you map three-word codes into the location reference fields your carrier system expects, or we provide codes as supplementary delivery instructions that drivers can opt to use.

How do we show the three-word code to customers in order confirmations and tracking pages?

iWeb builds code injection into your commerce platform's notification templates (email, SMS, tracking page). We ensure codes are clearly labeled and presented alongside the traditional address so customers understand the format.

Can customers edit their three-word code if it's incorrect, or do we have to manually intervene?

iWeb can embed a what3words map picker into your checkout or order detail page, allowing customers to view their code and refine the pin themselves before despatch. Changes flow back to commerce and downstream to the WMS.

How do we handle addresses in areas where what3words coverage is incomplete or unreliable?

iWeb helps you identify addresses where what3words encoding fails or returns unexpected results, and routes them to a manual review queue. You can override codes, use alternative location data (e.g., coordinates from a map picker), or flag the address as 'manual despatch only'.

What observability and alerting should we set up for the encoding pipeline?

iWeb instruments encoding success rate, API latency, timeout and rate-limit events, address validation failure rate, and manual exception queue depth. We set thresholds and alerts so your operations team is aware of encoding issues before they cascade to despatch delays.

If we replatform our WMS or switch 3PL providers, do we need to rebuild the integration?

iWeb designs the integration so that three-word codes are stored in commerce and WMS systems independently; switching systems requires remapping the despatch payload format, but the encoding logic remains the same. We plan the handoff to minimise disruption.

How do we handle international deliveries and non-English three-word codes?

what3words codes are language-agnostic; however, customer notifications and driver instructions may need to explain codes in local languages. iWeb handles translation and localisation of code presentation across your markets.

Can we encode bulk orders or historical orders after they've been captured?

Yes. iWeb builds batch encoding jobs that process orders in bulk via what3words API with rate-limit controls. Useful for backfilling historical orders or re-encoding addresses where the original code was invalid.

Who owns the decision of whether a code is mandatory or optional for a delivery?

iWeb helps you define the policy: codes may be mandatory for all deliveries, optional for some customer segments, or mandatory only for complex addresses (apartments, rural areas). Despatch and commerce teams jointly own the policy; iWeb enforces it in the integration.

How do we prevent duplicate or conflicting codes for the same delivery address?

iWeb implements caching and deduplication logic: if the same postcode or coordinates are encoded multiple times, we reuse the cached code. This reduces API calls and ensures consistency across orders.

Next step

Have a what3words integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →