Release note 25

Open OMS

Sourcing Hook

Customize your sourcing rules via your own external service to integrate your business constraints right from the candidate selection stage, while keeping your setup fully compatible with future OneStock platform update

Configure a sourcing hook on your rules to query an external endpoint:

Initial calculation: OneStock determines the list of eligible candidates based on the active rule.
Context transfer: OneStock transmits the list of candidates and full order context to your external service.
Custom processing: Your service applies its business logic and returns the adjusted candidate list.
Workflow resumption: OneStock continues standard orchestration using the candidates validated by your service.

What this update changes in practice:

Realtime severe weather management: Dynamically exclude warehouses and stores located in areas affected by weather alerts.

🔎 Documentation

Open OMS

Secret Manager

Manage all the keys that secure your integrations in a single place, with full visibility over their usage.

The Secret Manager prevents you from exposing plain-text credentials across your configurations:

Creation: Store your secrets in an encrypted vault directly from the OneStock interface.
Referencing: The system generates a unique identifier (HashKeyID) for each stored secret.
Usage: Enter this identifier in your workflow settings (Sourcing Hooks, Webhooks) instead of entering raw data.
Maintenance: Update a secret's value in a single location to instantly propagate the change across all integrations that reference it.

What this update means:

Sourcing Hook request signing: Each HTTP call sent to your hook endpoint is signed using the secret referenced by the HashKeyID configured on the hook. The receiving system can verify the request's authenticity and integrity — ensuring the call genuinely originates from OneStock and has not been tampered with in transit.

Store experience

Automatic printing

Speed up in-store fulfillment by automating the printing of your logistics documents.

With this new configuration, when a store associate validates an order on the fulfillment pages (Pack, Bag, Pack-scan, Bag-scan), everything happens automatically:

OneStock generates all documents configured for the order: shipping label, delivery slip, etc.
Each document is sent directly to your in-store printers (requires middleware implementation).
The order is validated without any additional steps required.

(Note: It is still possible to keep the process in manual mode.)

What this update changes in practice:

Ship-from-Store peak periods: Handle massive order volumes (Sales, Black Friday) by eliminating all unnecessary clicks during packing

To enable the feature, you have to configure it in the OneStock backoffice

🔎 Documentation

Open OMS

Smart ACL troubleshooting

Reduce investigation time for new integrations. When an API call is blocked by an access restriction, your IT teams and integrators no longer need to guess the cause or search through the documentation: they are guided straight to the answer.

We have simplified ACL error investigation—each error now points directly to the Troubleshooting Center. To enable self-diagnosis, an AI-powered button provides a plain-language explanation of the issues encountered. Technical teams can identify permission issues or errors on their own as soon as they encounter a blocker.

What this update changes in practice:

Shorter onboarding timelines: Enable your IT teams and integrators to self-diagnose ACL, carrier, or workflow errors.
Less back-and-forth between technical teams and support tied to basic integration and permission issues.

🔎 Documentation

Customer Promise

Configure the Delivery Promise faster

Accelerate your delivery promise setup by drastically cutting down the time required to adjust complex carrier rules and store timetables.

You can now bulk-edit transit times directly within the routes table, which loads significantly faster for complex configurations. Furthermore, any updates to store timetables or carrier closures propagate instantly across the system. This completely removes the need for manual recalculation.

What this update changes in practice:

New carrier onboarding: Set up dozens of regional routes in minutes by applying standard delivery times directly to them.
Adjustments for peak periods: Instantly extend transit times across an entire network to anticipate Black Friday or holiday slowdowns

And much more…

OneStock Backoffice

✨ Improved stability during migration of key features : Delivery Promise, Orchestration

✨ Display now handles linebreak

🐛 Fixed delivery routes not displaying in the backoffice

🐛 Empty parcels will now be completely displayed in the backoffice

🐛 Delivery configuration export is possible for thousands of routes

🐛 Bundles items can be modified in the backoffice

🐛 Scheduled event actions can be no effect

Items

🐛 Improve item updates synchronization

Shopify Connector by OneStock

🐛 Shopify ORDERS_CREATE and ORDERS_UPDATED webhook subscriptions remain active after the offline access token expires

🐛 Webhook IDs are correctly displayed on the Webhooks Management page

✨ Shopify and OneStock webhooks are processed by a dedicated worker, with duplicate detection and automatic retry on temporary errors

✨ Stock synchronisation uses Shopify GraphQL Bulk Operations, reducing the number of API calls on large catalogues

✨ Storefront extensions migrated from React to Preact, reducing bundle size

✨ App proxy response format is now controlled by an explicit output_format parameter

Store App

🐛 Fixed order disappearing from the store app after claiming
🐛 The address form in the OIS now saves addresses correctly

🐛 The date filter works properly on the Store App home page

🐛 Quantities displayed during return creation in the Store App are now correct

✨ UI adaptation for standalone mode on the Store App

Order lifecycle

✨ Delivery promise prediction with futur stocks is now more consistent and precise

✨Improved matching on zones of the delivery promise

🐛 Fixed silent error when orchestrating stock location without coordinates

🐛Fixed non orchestration orders in rules over

Legend : ✨ new feature / 🐛 bug fix

Technical API changes

API updates

For endpoint GET /items, using field "sales_channel":"true" overload all "sales_channels_features" values in the field "fields"

Influence the future of OneStock

Hey you, yes you! At the product team, we are looking to connect with you, our user, to learn about how you work with OneStock and shape the future of retail together.
So would you be interested in helping us out?

Collaborating is easy, simply click on the link below and pick a 30min time slot to get in touch with our product team.

Talk to you soon,

The OneStock Product Team

📅 Schedule a discovery call

Page updated

Report abuse