MRW integration for Spanish carrier labels and tracking
MRW handles transport. myFulfillment runs the work before collection: orders in one queue, checked warehouse preparation, service selection, a PDF label and a shipment number stored with the parcel. The Boostmyshop module uses your active MRW business account.
Carrier label
1.2 kg
- Boostmyshop product
- myFulfillment
- Category
- Carriers
- Connects
- Services allowed by your MRW contract
- Account required
- Active MRW business account · Boostmyshop module configured during onboarding
- Integration cost
- Boostmyshop module included with myFulfillment
- Sync frequency
- When each shipment is created and confirmed
- Data direction
- Shipment data to MRW · label and tracking to myFulfillment
- Developed by
- Boostmyshop
- Supported by
- Boostmyshop
- Sovereignty
- MRW, a Spanish company
- Vendor
- MRW
- Last updated
- 2026-09-11
How MRW fits with myFulfillment
What is MRW?
MRW is a Spanish carrier offering home and office delivery, several urgent service levels and routes beyond its domestic market. MRW also publishes its own modules for OpenCart, PrestaShop, WooCommerce, Magento and Shopify. Those modules cover one storefront at a time. myFulfillment addresses a different operation: several sales channels feed the same warehouse flow before the Boostmyshop module creates MRW shipments. The allowed service, address and parcel data go to the carrier; the PDF label and shipment number return to the shipping record.
Your operations cover orders, stock updates, barcode checks, and label creation.
Prepares shipment data and prints the MRW label at packing.
Parcel handed over to MRW.
MRW in your multichannel fulfillment flow
Orders from any sales channel already connected to myFulfillment can follow the selected warehouse flow and then ship with MRW. The carrier receives only the parcel data it needs; order and inventory management remain in myFulfillment.
myFulfillment runs the picking, MRW prints the label
For an MRW shipment, myFulfillment sends the parcel data, retrieves the PDF document and attaches the label to the confirmed shipment.
See the featureMRW returns a shipment number when the label is created. myFulfillment stores it with the parcel for customer service and shipping confirmation.
MRW number received when the label is created
See the featureFor MRW, myFulfillment reads the configured prices for services allowed on the account and estimates delivery dates. It does not present these amounts as a public carrier rate quote.
See the featureOrders intended for MRW join the same OMS queue as other connected orders. The team filters them, selects the warehouse and releases each order for fulfillment before creating the parcel.
Orders received from connected channels before the MRW shipment is created
See the featureAfter an MRW parcel is fulfilled, myFulfillment applies the movement to available inventory for the relevant channels. The carrier does not become the inventory system.
See the featureAn order assigned to MRW can follow a cross-docking flow in myFulfillment: receiving, checks, parcel assignment and label generation without an intermediate putaway.
See the featureWhat syncs, and when
| Data | When |
|---|---|
| In | |
| Order ready for fulfillment | after the sales-channel import |
| MRW label in PDF format | in the shipment-creation response |
| MRW shipment number | with the created label |
| Out | |
| Address, parcel and MRW service | when the shipment is created |
| Available channel inventory | after the inventory movement is processed |
When MRW is enough, and when myFulfillment makes the difference
MRW fits merchants shipping from the Iberian Peninsula. The Boostmyshop module becomes useful when the label must sit inside a multichannel fulfillment process run by the warehouse.
- Shipment creation, PDF label and MRW number held in the parcel record
- Several MRW services available to configure
- Orders from several channels fulfilled in the same OMS and WMS
- An MRW business account and active contract services are still required.
- The module uses prices configured in myFulfillment, not a public rate table queried in real time.
- Returns are handled on MRW's own platform and storefront options stay in the MRW modules.
| Solution | Multichannel orders | Warehouse fulfillment | MRW label | Shipment number | Carrier selection rules | Configured price and estimated date | Stock recalculated after shipping | MRW account required |
|---|---|---|---|---|---|---|---|---|
MRW with myFulfillmentRecommended | Supportedone queue for connected channels | Supportedrules and checks before shipping | SupportedPDF attached to the shipment | Supportedstored with the parcel | Supportedbased on operating configuration | Supportedprices configured for allowed MRW methods | Supportedto connected sales channels | MRW business account |
MRW e-commerce module | Not supportedone storefront per module | Not supportedno shared WMS flow | Supportedfrom the storefront | Supportedin the relevant storefront | Partially supportedchoice within one storefront | Partially supportedservice chosen at checkout | Not supportedoutside the shipping module | MRW business account |
MRW portal alone | Not supportedentry outside sales channels | Not supportedfulfillment outside the portal | Supportedfrom the portal | Supportedin the portal | Not supportedparcel-by-parcel choice | Partially supportedseparate lookup in the portal | Not supportedoutside the carrier portal | MRW business account |
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 MRW integration fits into your operations
How our customers use MRW day to day
Day to day, the team stays in its warehouse flow instead of entering every parcel in the MRW portal. Staff handle orders from stores and marketplaces in myFulfillment, check the contents, apply the carrier rule and print the label at packing.
Orders from several channels enter the same queue. Destination, weight and the customer promise then determine which configured MRW service is assigned.
Once the address and parcel are checked, myFulfillment creates the MRW shipment, retrieves the PDF and attaches it to the record used by the operator.
The MRW shipment number stays with the parcel. Customer service and confirmation feeds therefore use the same reference.
Printing orders. Cutting them apart with scissors. Dispatching manually across two countries.
Algorithmic splitting. Integrated labels. Real-time tracking on 25+ channels.
Read the full storyConnect MRW to your other tools, via myFulfillment
myFulfillment sits in the middle, so MRW can create labels for orders received from your sales channels. A few live pairings below.
Connect MRW to myFulfillment, step by step
- 1Open or confirm your MRW business account and the services allowed by your contract.
- 2During onboarding, ask the Boostmyshop team to enable the Boostmyshop module for MRW.
- 3Map your shipping methods to the MRW services used by your operation.
- 4Configure contract prices and selection rules by zone, weight and delivery promise.
- 5Test one order, the label PDF and the shipment number before processing live orders.
An active MRW business account is required. The Boostmyshop module covers shipment creation, the PDF label, the shipment number and services configured for the account. Storefront modules published by MRW keep their own options. Returns are handled on MRW's own platform.
MRW: frequently asked questions
Pricing, contract, carriers, Shopify, pickup points, worldwide selling and shipping: answers on the MRW integration.
The Boostmyshop team enables the Boostmyshop module during onboarding. You then map shipping methods to the MRW services allowed on your account, configure contract prices and test one complete shipment.
Yes. The module uses your existing carrier relationship. MRW opens the account and defines available services; Boostmyshop configures the shipping flow in myFulfillment.
Yes. myFulfillment sends the parcel data to MRW, retrieves the PDF document and attaches it to the shipment. The operator can then print it within the packing flow.
Configurable services include Urgente Hoy, Urgente 12, Urgente 19, Económico, 48 horas Portugal and Envío 24 horas domicilio. The actual choice depends on services enabled for your MRW account.
It retrieves the shipment number returned when the label is created and stores it with the parcel. That reference then supports shipping confirmation and customer service.
The module uses prices configured in myFulfillment for allowed MRW services and estimates their delivery dates. It does not query a public MRW rate table in real time.
MRW publishes modules for several platforms that send orders from that storefront into its systems. myFulfillment adds an OMS and WMS shared by multiple channels, with fulfillment, checks and carrier rules before the label.
No. Returns are handled on MRW's own platform, while myFulfillment manages the warehouse return record. Connecting the two is a specific project.
Explore other integrations
MRW covers shipping. Connect your sales channels and tools too.
MRW integration for Spanish carrier labels and tracking
See it in your own setup

