Shipping Providers
Shipping Provider apps integrate Hantera's delivery model with external carrier and checkout-options providers. Each shipping app:
- Calls the provider's API to fetch the shipping options (carrier products, delivery methods, pickup points) available for a given delivery.
- Implements the standard portal
shippingProductsServiceso the Select shipping product flow in the order view returns provider-specific options. - Exposes a reusable Filtrera module so other apps — for example a Commerce ↔ checkout-iframe bridge — can fetch options from their own ingresses without duplicating the provider integration.
Provider-specific configuration (API credentials, environments) is exposed via app settings, and per-channel configuration (e.g. an account or configuration id) is exposed as fields on the channel via a channel-editor extension.
Available Shipping Apps
nShift Checkout
Fetches shipping options from nShift Checkout. Owns OAuth token acquisition/caching and session creation; consumers only call the module's fetchShippingOptions entry point.
Key features:
- Public Filtrera module (
nshift.module.hrc) other apps can import. - Portal
shippingProductsServiceimplementation backed by a private ingress. - Channel-editor extension for the per-channel
nshiftCheckoutConfigurationId. OnNShiftCheckoutVariablescustom hook — let merchant rules contribute the provider-specificvariablesrecord on every lookup.