OneStock features integrations with multiple carriers. Carrier integrations can be managed directly from the Order Management Center. Depending on the carrier, the configuration will be form-based or code based. Carrier configuration feature the use of test values, which allow overriding initial value by test ones.
Carrier configurations can be set at the site level and overridden per stock location, for example, in case credentials are not the same between all your stock locations.
Site level configurations
General carrier configurations
This is configurations that impact all carriers. For example, you can set the default carrier that should be used in case none is set in the order.
New generation carrier configurations (form-based)
If the carrier exists both in legacy and MCU versions, for the MCU version to start being used, it must be added to the list of MCU carriers in the General Configurations > Advanced Options
This is the configuration section for our latest carrier generation, featuring our form-based configurations screens.
To start configuring a carrier you just need to add it at start setting it up.
Required fields are flagged with a *. Make sure to set them up.
Code based carrier configurations
If the carrier exists both in legacy and MCU versions, for the MCU version to start being used, it must be added to the list of MCU carriers in the General Configurations > Advanced Options
We strive to progresively support a larger number of carriers in the form-based format. In the meanwhile, those not yet included in the former are supported in code-based format.
Stock location overriding
Site configurations can be overridden per stock location