Configure Torevo • Packeta SK
Connect a Packeta account, map Shopify delivery methods and verify Slovak pickup points, labels, tracking and fulfilment.
- Type
- Standalone Shopify app
- Status
- App review in progress
- Last updated
- 21 July 2026
- Markets
- SK
- Access
- Access arranged with Torevo
On this page
Torevo • Packeta SK is a standalone Shopify app for Slovak Packeta pickup delivery. Its own installation keeps account access, method mappings, pickup selections, shipment state, labels and tracking together in Shopify Admin.
“Packeta” identifies compatibility with the carrier service. Torevo is an independent integration and does not claim an official partnership unless separately confirmed in writing.
See the workflow in Shopify
The dashboard keeps connection, market profile, mapping, selector and operational readiness in one checklist. A configured store can verify every required setup step before creating its first shipment.

Settings explain the boundary between the write-only server API password and the public Widget key without displaying the saved private credential.

The Orders page brings payment, mapped delivery, selected pickup destination, readiness and the shipment action together. Unknown mappings remain blocked instead of being guessed.

What you need from Packeta
Open Packeta Client Section and prepare:
- the private 32-character API password for server operations,
- the public 16-character Widget API key for the customer pickup selector,
- the exact sender label shown under User information → Senders,
- an account enabled for the Slovak services you plan to offer.
Packeta does not provide a sandbox. A dedicated test account still uses the production API endpoint. The API password is encrypted and write-only in Torevo. The public Widget key is published only to the configured selector.
Connect and verify the account
- Open Torevo • Packeta SK → Settings.
- Enter an internal account label, API password, Widget API key and exact sender label.
- Keep the Packeta Slovakia profile enabled and save.
- Select Validate Packeta Slovakia connection.
The result reports credentials, sender label and Widget configuration separately. Fix a failed item before mapping shipping methods or creating a shipment.
Map delivery methods deliberately
Create an explicit mapping for every Shopify shipping method you support. Use separate mappings for a Packeta pickup point and Z-BOX when both are offered. Do not map home delivery or another service unless the app lists it as supported.
If a Shopify rate is renamed or recreated, update the mapping and place another test order. Unknown methods are blocked instead of being guessed.
Activate and test the pickup selector
In Online Store → Themes → Customize, add the Torevo pickup-selector app block to the cart template. The app supplies the Slovak profile automatically. No country or provider selector is shown to the merchant or customer.
Test:
- a Slovak Packeta pickup point,
- a Slovak Z-BOX,
- continuing without a required selection,
- a stale or invalid point ID,
- cart reload and English, Slovak and Czech storefront text.
Torevo validates the selected point again before shipment creation. Browser data alone is never accepted as proof that a point remains valid.
Verify the first shipment
Use a synthetic order with a Slovak destination, recipient contact, known weight and mapped shipping method. In Orders, review payment, delivery mapping, pickup point and readiness before selecting Prepare shipment.
After confirmation, open the shipment detail and verify:
- the Packeta packet and tracking identifiers,
- PDF and the configured ZPL/label workflow,
- tracking refresh and its mapped status,
- Shopify fulfilment only when explicitly requested,
- the safe audit timeline and retry/reconciliation actions,
- cancellation of the synthetic Packeta record after the test.
Automation and safe recovery
Enable automatic creation only after manual prepaid and COD tests pass for every shipping method. Keep batch sizes small initially.
For a timeout or unknown provider outcome, use reconciliation before retrying. Torevo must not create a second packet until it can prove the original request did not succeed. Use the safe support bundle for diagnosis. Never send credentials, labels, full customer data or raw provider responses.