When an order has a selected pickup point, the pickup point information is stored in the order metafield (atlas_pickup_points.point). This is always active and requires no configuration. For details on the metafield structure, refer to our integration guide.
Some systems are already pre-integrated and read pickup point data automatically. See the integrations page for a full list.
Additional integration options
Most third-party systems (shipping label apps, order management systems, warehouse management systems, etc.) expect pickup point details in a specific format. Depending on what your system requires, you can enable one or more of the following options in the pickup point configuration. All options update the order within seconds after it is created.
1. Order custom attributes
Order custom attributes (also known as note attributes) are key-value pairs of extra data attached to the order. This is the most common way third-party systems read pickup point details.
To set this up:
- Check with your third-party system which custom attributes it expects (e.g., attribute name and value format).
- In Shopify Admin → Atlas Pickup Points, open the pickup point configuration and enable Order custom attributes.
- Define the attributes to match what your third-party system requires. You can use variables like
{{ point.code }},{{ point.provider }},{{ point.address.address1 }}, etc.
2. Shipping address update
By default, orders are placed with the shipping address the buyer enters, not the pickup point address. If you enable Update shipping address in the pickup point configuration, Atlas will update the order’s shipping address with the pickup point location.
By default, Atlas updates:
- Address line 1 (street and number)
- City
- Postal code
- Province
- Country code
It does not include the pickup point code (ID) or provider (carrier) by default. If your system needs these, check Customize how shipping address is updated to control three address fields:
- Company (default: empty)
- Address / address line 1 (default:
{{ point.address.address1 }}) - Apartment, suite, etc. / address line 2 (default: empty)
For example, if your system expects the pickup point code in address line 2, enter {{ point.code }}. You can also combine multiple variables in a single field, e.g., {{ point.provider }} {{ point.code }}.
3. Custom order metafield
If your third-party system can read order metafields, it should use the standard Atlas metafield (atlas_pickup_points.point), which is always active and requires no configuration. See the integration guide for the metafield structure.
If it requires a different namespace, key, or value format, contact us with:
- App name and link
- Metafield namespace and key
- Expected value format