Daily shipment operations

Use this guide after connecting the carrier and testing shipping-method mappings. It applies to the supported Packeta Slovakia and Zásilkovna Czechia modules inside one Torevo Shipping application.

Before creating a shipment

An order is ready when it has:

• a supported and explicitly mapped shipping method,
• a valid pickup point or Z-BOX when required by the service,
• the delivery data required by the selected service,
• a supported country, currency and service combination,
• a COD amount and currency matching the order when COD is used,
• a state that permits dispatch under your operating rules.

If validation fails, correct the source data or mapping. Do not create a shipment in the carrier portal and then submit it again from Torevo unless you use a controlled existing-record attachment flow.

Manual creation

1. Open the order and the Torevo Shipping block or action in Shopify Admin.
2. Review the module, service, pickup point, weight, COD and contact data.
3. Select Create shipment once.
4. Wait for acceptance. Reconcile an unknown or delayed outcome first.
5. After acceptance, open the label and verify the tracking number.

The app uses idempotent operations. A repeated click or worker should not create a second shipment, but an unknown remote outcome must still be reconciled instead of retried blindly.

Automatic creation

Enable automation only after successful tests for every shipping method you use. A rule must have one clear trigger, module, service and set of order conditions.

Recommended rollout:

1. test the manual flow with a synthetic order,
2. enable automation for one supported shipping method,
3. observe the first operations and error queue,
4. add services gradually,
5. keep the kill switch available.

An unknown service, missing pickup point or invalid COD must fail to merchant review rather than be guessed.

Batch processing and labels

Select only orders with the same ready workflow in a batch. Confirm the selected count before starting. Evaluate the result per item; never repeat a partially successful batch as a whole.

Depending on the supported module, you can download PDF, ZPL or a combined batch file. Confirm the format and target printer before printing. Labels contain personal data, so store and share them only for as long as necessary.

Tracking and Shopify fulfilment

Refresh tracking from the shipment detail or allow the scheduled synchronisation to run. Carrier status and Shopify fulfilment status are different: one describes transport and the other communicates order fulfilment in Shopify.

When fulfilment creation is enabled, verify:

• the correct line items and quantities,
• tracking number and URL,
• that another system has not already fulfilled the order,
• that customer notification matches your operating policy.

Cancellation and changes

Cancel only while the carrier state supports cancellation. After acceptance, check both the carrier and Shopify state. Cancelling a shipment does not automatically refund the order or cancel its fulfilment.

If the address, service, COD or pickup point changed, do not silently edit a shipment already accepted by the carrier. Use a supported update or a controlled cancellation and recreation flow.

Reconcile an unknown outcome

Use reconciliation after a timeout, delayed response or any state where carrier acceptance is unknown. The application should first look for a safe, unique match. An ambiguous result stays in manual review.

Send support the shop domain, safe operation or shipment ID, timestamp, module and visible error code. Never send the API password, full customer record or a label image unless requested through an approved secure channel.

Daily checklist

• Review operations in Needs attention.
• Reconcile timeouts before retrying anything.
• Inspect partially successful batches one shipment at a time.
• Watch for unusually long tracking or label delays.
• Regularly verify carrier access and service mappings.
• Run another test order after changing Shopify shipping methods.