Skip to content
This repository has been archived by the owner on Jan 10, 2025. It is now read-only.

DEVDOCS-5284 [new]: Shipping Provider API, clarify truncated postcodes #2074

Merged
merged 2 commits into from
Oct 13, 2023
Merged

DEVDOCS-5284 [new]: Shipping Provider API, clarify truncated postcodes #2074

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9f16c1e
add when wallets truncate postcodes, make heading
bc-andreadao Oct 10, 2023
87a2be8
copyedit
bc-andreadao Oct 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/api-docs/store-management/shipping/shipping-provider-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -496,8 +496,12 @@ When you uninstall an app with an associated shipping carrier, you also automati
The response payload will display shipping quotes from lowest to highest price.
</Callout>

### Incomplete postcodes

Shipping provider integrations should plan to handle incomplete postcodes when handling shipping quotes. Incomplete postcodes can occur when stores use [digital wallets](https://support.bigcommerce.com/s/article/Online-Payment-Methods?language=en_US#digital-wallet) as a payment method. Digital wallets truncate postcodes for shipping addresses in the UK and Canada as they only provide the first three characters to shipping provider integrations.

Digital wallets truncate postcodes only when they generate shipping quotes. Complete postcodes are available once a shopper places the order. Shipping providers can read and fetch order data after order placement.

## Including product metadata in rate requests

BigCommerce passes carrier-specific product metadata to a carrier service in a rate request via product and variant metafields. This product metadata can be useful if your service depends on specific fields that are not existent on BigCommerce products or variants by default.
Expand Down