What common problems do warehouses face when shipping with OnLogistics?
Warehouses that ship with OnLogistics often manage a mix of domestic and international consignments with tight cut offs and varied delivery promises. The pressure point at the bench is not printing a label, it is choosing the correct OnLogistics service for each order quickly and consistently. The correct choice can change with the total order weight, the total order value, the delivery postcode, and the destination country. When those decisions rely on memory or desk guides, small mistakes creep in and slow the flow.
Typical issues include misreading a postcode segment, totalling the wrong weight across multi line orders, or overlooking a value threshold that should trigger a signature or enhanced cover. These slips become relabelling, manual carrier changes, missed departures, or delivery failures that generate customer service work. During peaks, every manual check adds seconds, queues form at the bench, and throughput becomes sensitive to who is on shift.
Clarus WMS removes this friction by automating carrier and service selection for OnLogistics. Instead of asking packers to decide order by order, you define clear rules once and Clarus applies them to every shipment. The system calculates order totals, checks address details, evaluates your conditions, and assigns the correct OnLogistics service automatically. Labels, tracking, and shipment records follow in the same workflow. Any time saving or efficiency figures on this page are estimates, because the exact impact depends on your order mix, staffing, and layout.
How can a WMS automate carrier selection for OnLogistics shipments?
In Clarus, carrier assignment is native. You map your shipping policy to a set of rules, and Clarus evaluates each order against those rules the moment it is ready to ship. The rules engine works with four core inputs that exist on every sales order, total order weight, total order value, delivery postcode, and destination country. Based on those inputs, Clarus can assign OnLogistics and select the correct service automatically. No middleware is required for the capabilities described here, and you do not need custom development to configure the logic.
The workflow is simple and repeatable. First, Clarus receives the order from your commerce platform or ERP. Second, Clarus calculates totals across all lines, so the full weight and order value are correct without manual arithmetic. Third, Clarus evaluates the delivery address, including postcode and country. Fourth, Clarus compares those inputs to your rule list and assigns the matching OnLogistics service. Finally, Clarus generates the label and tracking in the same workflow and records the shipment while keeping inventory movements in sync. Packers see the service already chosen, confirm the pick, print the label, and move the parcel on without extra checks.
Esta automatización reduce el tiempo de decisión y las tasas de error. Si su política cambia, por ejemplo, un nuevo umbral de valor o una excepción de código postal, actualiza la regla una vez y todos los pedidos futuros seguirán la nueva ruta. Si los volúmenes aumentan, las reglas continúan aplicándose instantáneamente, por lo que el rendimiento de referencia se mantiene más estable incluso cuando rota personal o incorpora nuevos empleados. Los supervisores pueden revisar qué reglas se aplicaron a qué pedidos, por lo que los resultados son explicables y las mejoras son más fáciles de validar.
Can Clarus assign OnLogistics services based on weight, value, or delivery location?
Yes. Clarus can assign OnLogistics services using rules that evaluate total order weight, total order value, delivery postcode, and destination country. These conditions cover real world scenarios and can be combined or prioritised to match your policy. The rule builder uses plain language fields, so configuration is accessible to non technical users. Here are practical examples to illustrate the pattern. Treat them as examples rather than templates, since your thresholds and service mix will be specific to your operation.
• Route light domestic parcels to a standard OnLogistics option when total order weight is below your threshold and the postcode is within standard coverage.
• Aplica automáticamente un servicio de compensación firmado o mejorado cuando el valor total del pedido supera un límite definido, manteniendo la misma velocidad para que la experiencia del cliente siga siendo coherente.
• Use a timed or morning service for selected postcode ranges where delivery windows are expected or where performance warrants a specific option.
• Direct all non United Kingdom destinations to an appropriate international pathway by using the destination country condition, while leaving domestic rules unchanged.
• Permitir una regla de entrega los sábados que solo se aplique cuando la fecha de entrega solicitada sea sábado y el código postal sea elegible, mientras que los días de semana sigan su lógica estándar.
Debido a que Clarus calcula los totales a partir de las líneas de pedido, los empaquetadores no necesitan sumar pesos o valores en el banco. Esto evita errores de casos extremos, como omitir un artículo pesado en un pedido con varias líneas o leer mal un punto decimal. Si su política contiene excepciones de códigos postales, la condición de código postal las captura sin depender de la memoria o tablas de consulta separadas. Cuando más de una regla podría coincidir con un pedido, se establece el orden de las reglas para que las salvaguardias se ejecuten antes que las reglas generales.
Any efficiency or cost saving claim should be treated as an estimate. Many teams find that removing manual checks reduces decision time and relabelling, others see the main gain in fewer exceptions and simpler training. Exact results depend on your processes and the services you enable with OnLogistics.
Do I need custom development to use OnLogistics with Clarus WMS?
No, not for the functionality described here. Clarus provides native automation for assigning OnLogistics and selecting services based on total order weight, total order value, delivery postcode, and destination country. Configuration happens in the Clarus dashboard with plain language controls. You can create and edit rules, test scenarios with example orders, set rule priority, and enable changes without writing code. Once saved, the next eligible orders follow the updated logic.
You also do not need middleware for these capabilities. By keeping carrier assignment, label generation, tracking, and inventory updates inside Clarus, you remove an extra layer that can fail or drift from policy. Teams gain a single place to define and audit how OnLogistics is used. Training becomes simpler because staff learn one workflow, and the chance of unofficial workarounds reduces across sites and shifts.
Si su política evoluciona, usted extiende el conjunto de reglas en el mismo lugar. Por ejemplo, agregue una nueva excepción de código postal, ajuste un peso o umbral de valor, o combine condiciones para capturar un nuevo caso límite. Los supervisores pueden revisar qué regla se aplicó a cada pedido, por lo que los resultados son explicables y las mejoras son más fáciles de validar. Cualquier declaración sobre el tiempo de configuración es una estimación, ya que las operaciones difieren en la calidad de los datos y la combinación de servicios, pero los pasos son sencillos.
How does Clarus keep orders, labels, tracking, and inventory aligned for OnLogistics?
Clarus keeps the shipping workflow in one system so data stays aligned. Sales orders flow into the WMS. Inventory updates as picks are confirmed. When an order is ready to ship, the OnLogistics assignment has already been made by your rules. Clarus then generates the label and tracking and records the shipment against the order while updating inventory at the same time. This removes copy and paste steps and reduces the chance of mismatches across systems.
At the bench, packers see a single screen that guides the task. Because the service selection is made upstream, the focus is on confirming picks and printing labels rather than checking eligibility. For supervisors, the benefit is visibility. You can see rule definitions, rule order, and which orders matched which rules. That makes it easier to refine policy and to explain outcomes to colleagues and customers. Customer service teams benefit from the same clarity when answering delivery queries.
Si ocurre una excepción, el rastro de auditoría dentro de Clarus te ayuda a encontrar y corregir la causa raíz sin tener que cambiar entre múltiples herramientas. Puedes rastrear qué regla se aplicó, si se cumplió un umbral y si una coincidencia de código postal activó un camino específico. Esto apoya la mejora continua y reduce el tiempo dedicado a las investigaciones.
¿Cómo es la configuración y qué tan rápido podemos empezar a operar?
Setup follows a structured sequence that most teams complete without developers. First, review your current OnLogistics usage, including which services you use, your common thresholds for weight and value, and any postcode or country based exceptions. Second, model that policy as rules inside Clarus using the native conditions for total order weight, total order value, delivery postcode, and destination country. Third, create a set of sample orders that reflect your real scenarios and test the rules in Clarus to confirm the correct service is assigned for each case. Fourth, enable the rules in your live environment and monitor the first shipments.
El panel de Clarus utiliza un lenguaje sencillo para definir condiciones y resultados. Puedes añadir descripciones a cada regla para que los colegas entiendan la intención. Si necesitas cambiar un umbral o añadir una nueva excepción de código postal, puedes hacer ese cambio tú mismo y probarlo de inmediato. Cualquier declaración sobre el tiempo de configuración son estimaciones, porque cada operación tiene sus propios datos, calendario y mezcla de servicios, pero los pasos son sencillos y repetibles.
La formación se centra en la nueva simplicidad en el banco de trabajo y el control para los supervisores. El personal aprende que el servicio ya está asignado, confirma la selección e imprime la etiqueta. Los supervisores aprenden a leer la lista de reglas, a reordenar las reglas si cambian las prioridades y a deshabilitar temporalmente una regla si un servicio se pausa. Esto proporciona control sin complejidad y reduce la dependencia de puntos de conocimiento únicos dentro del equipo.
Want a WMS that handles OnLogistics complexity for you?
If you want to remove manual service selection, reduce exceptions, and ship with more confidence, Clarus WMS is designed to help. You define straightforward rules once, Clarus evaluates every order and assigns the correct OnLogistics service automatically. Labels, tracking, and inventory updates live in the same workflow, with no middleware and no code required for the capabilities described here. The result is a calmer bench and a more predictable despatch profile. Any improvement figures are estimates, so the best way to judge impact is to try your own scenarios in a demo.
Book a short walkthrough and bring sample orders that reflect your OnLogistics usage. We will model your weight and value thresholds, postcode exceptions, and destinations as rules in Clarus and run them end to end so you can see the outcome in context.
Preguntas frecuentes
Can Clarus apply different OnLogistics services for different order profiles automatically?
Yes. You can define multiple rules that map different conditions to specific OnLogistics services. Clarus evaluates each order against your rule set and assigns the matching service. No custom development is required for the conditions described here.
¿Qué sucede si dos reglas pueden coincidir con la misma orden?
Estableces la prioridad. Coloca la política más importante primero, por ejemplo, una salvaguarda de alto valor, y Clarus aplicará esa regla antes que otras. También puedes combinar condiciones donde una combinación específica debe ser manejada por una sola regla.
¿Los empacadores todavía necesitan calcular el peso y el valor en el banco?
No. Clarus calcula el peso total del pedido y el valor total del pedido a partir de las líneas del pedido. Los encargados de embalar no necesitan sumar pesos ni comprobar valores manualmente, lo que reduce el riesgo de errores y agiliza el embalaje.
How are labels, tracking, and inventory kept in sync when shipping with OnLogistics?
Clarus genera la etiqueta y el seguimiento en el mismo flujo de trabajo que confirma la recolección y envía el pedido. El envío se registra contra el pedido y el inventario se actualiza al mismo tiempo, lo que mantiene los datos alineados sin copiar y pegar.
Do we need developers or middleware to go live with OnLogistics in Clarus?
No, no para la funcionalidad descrita en esta página. Clarus proporciona automatización y configuración nativa de asignación de transportistas en el panel de control que los usuarios no técnicos pueden administrar. Cualquier reclamación de plazos son estimaciones, pero el proceso es sencillo: revise su política, modélala como reglas, pruebe con pedidos de muestra y luego habilítela en producción.