Getting started with Torevo shipping apps

Torevo • Packeta SK and Torevo • Zasilkovna are two separately installed Shopify apps. Each has its own Shopify identity, subscription, runtime, database, provider account and settings. The shared Torevo Shipping foundation contains only tested code and operating rules—never accounts or data shared between stores.

1. Open the installed app

In Shopify Admin, open the exact app installed for your market and follow its setup guide. Prepare:

• a compatible carrier account with API access,
• the private API password used for server-to-server shipment operations,
• the public Widget API key used by the storefront pickup selector,
• the sender label configured in the carrier account,
• at least one Shopify shipping method that should use the app.

Never send credentials through email, chat or a support bundle.

2. Connect the carrier account

Open Settings, enter the account details and save. The API password is write-only: Torevo records whether it exists but never displays the saved value again. Run the read-only connection test and continue only when the credentials and sender label are verified.

Packeta does not provide a sandbox. A dedicated test account still uses Packeta’s production API endpoint, so test records must be handled and cancelled deliberately.

3. Map Shopify shipping methods

Create an explicit mapping for every supported Shopify shipping method and exact delivery service. The app never guesses a carrier service from a translated or renamed rate title. Unmapped methods stay blocked until a merchant reviews them.

4. Add the pickup selector

In Online Store → Themes → Customize, add the Torevo pickup-selector app block to the cart template. The installed app supplies its own market profile automatically. Customers do not choose between Packeta and Zásilkovna inside one app.

Verify that:

• only pickup points for the app’s market are shown,
• the selected point survives a cart reload,
• a clear message blocks a mapped pickup service when no point is selected,
• an unsupported or stale point fails safely.

5. Process one synthetic order

Create an order with a valid destination, email or phone, a mapped shipping method, known weight and—when required—a selected pickup point. Open Orders, review readiness and confirm shipment creation only after every check passes.

After creation, verify:

1. exactly one shipment exists in Torevo and the carrier account,
2. its tracking identifier belongs to that shipment,
3. the PDF or ZPL label can be opened again,
4. Shopify fulfilment changes only when explicitly enabled,
5. the audit timeline contains safe states without credentials or raw customer payloads,
6. the synthetic carrier record can be cancelled after the test.

6. Enable automation last

Start automation only after the manual workflow succeeds for every shipping method in use. Begin with a narrow trigger and small batch. Keep needs-attention and reconciliation states visible to the operator.

If a carrier request ends with an unknown outcome, do not repeat it blindly. Reconcile first and retry only after the app can prove that no remote shipment was created.

Getting help

Open the in-app support centre or the public support page. Include the safe shop identifier, shipment or batch ID, timestamp and safe error code. Never include API passwords, Shopify tokens, full addresses, customer contacts, labels or raw provider responses.