Swiss Post integration for labels and parcel references
The Swiss Post integration creates a label from a shipment prepared in myFulfillment, without re-keying the address in a carrier portal. The module keeps the consignment identifier returned with the document. Orders, warehouse checks and cross-dock flows remain in myFulfillment before the parcel is handed to Swiss Post.
Carrier label
1.2 kg
- Boostmyshop product
- myFulfillment
- Category
- Carriers
- Connects
- PostPac Economy and Priority, Saturday variants, bulky goods, Swiss-Express Moon, VinoLog and SameDay where enabled
- Account required
- Swiss Post billing relationship · API access, client ID, secret and franking license number
- Integration cost
- The Boostmyshop module is included with myFulfillment · carriage is billed through your Swiss Post relationship
- Sync frequency
- When a label is requested · sales-channel feeds follow their own configuration
- Data direction
- Shipment data to Swiss Post · label and consignment identifier returned
- Developed by
- Boostmyshop
- Supported by
- Boostmyshop
- Sovereignty
- Swiss
- Vendor
- Post CH Ltd
- Last updated
- 2026-09-11
How Swiss Post fits with myFulfillment
What is Swiss Post?
Swiss Post is Switzerland's national postal operator. For an e-commerce merchant, its role begins with carrying the parcel. myFulfillment manages the layer before that: orders from connected channels, allocation, preparation, checks and carrier-service selection. The Boostmyshop connector uses Digital Commerce API client authentication and the Barcode service to request a label with the address, weight, service and print settings. It then stores the returned document and consignment identifier. Tracking events, PickPost and shipping options are separate Swiss Post APIs, activated on their own.
Your operations cover orders, barcode checks, and label creation.
Prepares shipment data and prints the Swiss Post label at packing.
Parcel handed over to Swiss Post.
Swiss Post after Shopify, PrestaShop or WooCommerce
The store or marketplace supplies orders to myFulfillment. Once a parcel is prepared, the module requests the Swiss Post label and retains the returned identifier. Swiss Post is not the order-import connector; it enters the flow when the shipment is created.
myFulfillment runs the picking, Swiss Post prints the label
At packing, myFulfillment sends Swiss Post the sender, recipient, service, weight and parcel count. The returned label is stored as PDF, sPDF or ZPL2, according to the account setting.
See the featureSwiss Post returns a consignment identifier with the label. myFulfillment stores it on the shipment, where the team finds it next to the carrier document.
Identifier received with the label and kept on the shipment in myFulfillment
See the featureFor Swiss Post, the module compares prices configured on the carrier account for the available services. The amounts shown come from that configuration, not from a quote requested from Swiss Post at calculation time.
See the featureFor International Priority Plus only, the Swiss Post connector combines the RETR return code with the Priority service. Other return workflows must be confirmed during implementation.
See the featureSwiss Post does not import orders. Shopify, PrestaShop, WooCommerce or marketplace orders first enter myFulfillment, where the team selects the carrier service when the shipment is prepared.
Channel orders enter myFulfillment before Swiss Post is selected
See the featureOn a cross-dock flow, an item received for a waiting order is barcode-checked and packed in myFulfillment without long-term storage, then the Swiss Post label is requested when the parcel leaves.
See the featureWhat syncs, and when
| Data | When |
|---|---|
| In | |
| Store or marketplace order | when imported by that channel's Boostmyshop module |
| PDF, sPDF or ZPL2 label | in the label-creation response |
| Consignment identifier | in the same response as the label |
| Out | |
| Sender, recipient and weight | when the label is requested |
| Swiss Post service and options | when the shipment is created |
When Swiss Post is enough, and when myFulfillment makes the difference
Our operator's read: the connection is solid for creating a Barcode label and keeping its identifier in a multi-channel flow; Swiss Post's other APIs are activated on their own.
- A direct Digital Commerce API connection with client authentication
- Packing-station output in PDF, sPDF or ZPL2, from A5 to A7
- Specific Swiss services and options, including PostPac, Saturday, signature, VinoLog and SameDay
- Comparison uses prices configured in myFulfillment, not a live Swiss Post rate request
- The consignment identifier is stored on the shipment; tracking events go through the Track Consignments API
- PickPost and Swiss Post's other APIs are activated separately from the connector
| Solution | Swiss Post label | Orders from several channels | Barcode checks and cross-docking | Prices used for comparison | Consignment identifier attached to shipment | Tracking events and PickPost | Swiss Post label formats | International Priority Plus return |
|---|---|---|---|---|---|---|---|---|
Swiss Post via myFulfillmentRecommended | Supportedfrom the prepared shipment | Supportedcentralized before carrier selection | Supportedin myFulfillment | Supportedusing prices configured on the carrier account | Supportedin the label response | Not supportedthese Swiss Post APIs are activated separately | SupportedPDF, sPDF or ZPL2 according to the setting | Partially supportedRETR code combined with PRI for this method |
Swiss Post handled separately in each store | Supportedin each store's own tool | Not supportedeach store keeps its own queue | Not supportedbuilt outside the carrier step | Partially supporteddepending on the store tool | Partially supporteddepending on the store tool | Partially supporteddepending on the selected plug-in | Partially supporteddepending on each store's plug-in | Partially supporteddepending on the plug-in and method |
Comparison based on the official documentation and myFulfillment docs. The limit is stated under the "Partial" badge; no rating, no sponsored placement.
See how the Swiss Post integration fits into your operations
How our customers use Swiss Post day to day
In daily operations, Swiss Post becomes one step in the preparation flow instead of a second data-entry station. The operator works in myFulfillment, checks the parcel, selects an allowed service and receives the carrier document with its shipment reference.
After the parcel check, myFulfillment sends Swiss Post the address already held on the order, the weight, the service and the print settings. The document returns to the shipment.
The team can use PostPac Economy, PostPac Priority and other methods enabled for the account. The compared price comes from carrier-account configuration, not a live rate request to Swiss Post.
Swiss Post returns the consignment identifier with the label. myFulfillment attaches it to the shipment, where the team finds it without re-keying it from a carrier portal.
A product received for a waiting order is checked, prepared without long-term storage and labeled with Swiss Post on departure. Cross-docking remains a myFulfillment capability, not a carrier API feature.
Multi-channel orders to prepare, followed by parcel data re-entry for every carrier label.
Preparation stays in myFulfillment and the Swiss Post label is requested at the packing station.
Read the full storyConnect Swiss Post to your other tools, via myFulfillment
myFulfillment sits in the middle, so Swiss Post can create labels for orders received from your sales channels. A few live pairings below.
Connect Swiss Post to myFulfillment, step by step
- 1Open a Swiss Post business billing relationship and request Digital Commerce API access through the developer portal.
- 2In myFulfillment, enter the client ID, secret and franking license number without copying them into shared operating notes.
- 3Enable only the services and options covered by your Swiss Post relationship, then choose the paper size, file type and resolution.
- 4Test an order with its address, weight and service, then check the label and consignment identifier before opening the regular flow.
A Swiss Post business billing relationship and API credentials are required. The connector creates the Barcode label and keeps the identifier returned with that document. Compared prices come from carrier-account configuration. Tracking-event retrieval and PickPost point search belong to separate Swiss Post APIs, subscribed on their own. Service and option availability depends on the merchant's Swiss Post relationship.
Swiss Post: frequently asked questions
Pricing, contract, carriers, Shopify, pickup points, worldwide selling and shipping: answers on the Swiss Post integration.
You need a Swiss Post business billing relationship and Digital Commerce API access. In myFulfillment, the Boostmyshop module asks for a client ID, secret and franking license number. Test one label with a real address, weight and service combination before opening the regular flow.
The connector offers PostPac Economy, PostPac Priority, Saturday variants, bulky-goods methods, Swiss-Express Moon, VinoLog and SameDay. A method in the connector does not replace account eligibility. Enable only the services included in your Swiss Post relationship.
The connector offers A5, A6 and A7 paper sizes, PDF, sPDF or ZPL2 files, and 200, 300 or 600 dpi resolution. The chosen setting is sent when the Swiss Post label is created.
No. The comparison goes through the Swiss Post methods and reads the price configured in the myFulfillment carrier account. No rating request is sent to Swiss Post at calculation time.
The connector picks up the consignment identifier returned with the label and stores it on the shipment in myFulfillment. Detailed journey events belong to Swiss Post's Track Consignments API, subscribed on its own.
Swiss Post publishes PickPost as a separate API, which the current connector does not call. If pickup-point choice is essential at checkout, plan that flow from the start of the project.
For this method only, the connector combines the RETR code with the PRI service during label creation. Other Swiss Post methods do not have this return flow preconfigured; each case depends on the service and your contract.
No. The sales channel's Boostmyshop module imports the order into myFulfillment. The team then prepares the parcel and selects Swiss Post as the carrier. This separation lets the same carrier connection serve eligible orders from several channels.
Explore other integrations
Swiss Post covers shipping. Connect your sales channels and tools too.
Swiss Post integration for labels and parcel references
See it in your own setup

