PHPackages                             wexo/module-webshipper - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. wexo/module-webshipper

ActiveMagento2-module

wexo/module-webshipper
======================

Webshipper Magento2 Module

1.0.6(9mo ago)116.7k↓43.5%5[5 issues](https://github.com/wexo/module-webshipper/issues)proprietaryPHP

Since May 10Pushed 9mo ago6 watchersCompare

[ Source](https://github.com/wexo/module-webshipper)[ Packagist](https://packagist.org/packages/wexo/module-webshipper)[ RSS](/packages/wexo-module-webshipper/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (9)Dependencies (2)Versions (29)Used By (0)

User Guide
==========

[](#user-guide)

Setup
-----

[](#setup)

For the Webshipper setup to work we need to connect Webshipper to Magento and visa versa. This will be done by Creating an `Order Channel` in Webshipper and connecting it to Magento via a `System Integration` which supplies Webshipper with an `API_TOKEN` which can be used by Webshipper to communicate with your Magento platform.

Likewise in order to allow for your Magento platform to communicate with Webshipper we need to take the `Configuration Token` generated by the `Order Channel` and supply it in Magento.

### Create Order Channel

[](#create-order-channel)

To create an order channel navigate to your Webshipper installation and click on `Connect` then `New order channel`. Select Magento 2 and click `Connect`

[![Order Channel Creation](/readme/webshipper_create_order_channel_magento2.png)](/readme/webshipper_create_order_channel_magento2.png)

Fill out `Name`, `Url`, `Access Token`, `Store Id` as shown here:

[![Order Channel Creation Form](/readme/webshipper_create_order_channel_information.png)](/readme/webshipper_create_order_channel_information.png)

If you do not know how to get your `Access Token` you can generate one by going to `System => Extensions => Integrations` in your Magento admin panel

[![Magento 2 Integration Path](/readme/webshipper_integration_path.png)](/readme/webshipper_integration_path.png)

[![Magento 2 Access Token](/readme/webshipper_integration_api_token.png)](/readme/webshipper_integration_api_token.png)

Then create a new integration named `Webshipper` and give it access to your system. After creation you need to approve the new integration, afterwards it will generate a token for you. Copy the Access token and paste it into Webshippers Order Channel and click Create.

Webshipper will now attempt to communicate with Magento and if all goes well the `Order Channel` is now ready for use.

#### Setup Configuration Token

[](#setup-configuration-token)

In order for Magento to communicate with Webshipper we need to setup the Configuration token in Magento.

Go to your `Order Channel` and copy the `Configuration Token`. You can find it under `Connect => Select an Order Channel => Information`.

[![Webshippers Configuration Token](/readme/webshipper_configuration_token.png)](/readme/webshipper_configuration_token.png)

Paste the `Configuration Token` into your Magento Backend under `Stores => Configuration => Sales => Delivery Methods => Webshipper => Webshipper Configuration Token`.

[![Webshippers Configuration Token](/readme/webshipper_rate_quotes_configuration_token.png)](/readme/webshipper_rate_quotes_configuration_token.png)

### Delivery Methods ( `rate_quotes` )

[](#delivery-methods--rate_quotes-)

In order for webshipper to understand your `Order`'s Shipping method we need to couple the shipping rates from Webshipper to your Magento. Once you have setup your `Configuration Token` it should work out of the box. However if you wish to change certain settings when requesting Delivery Methods, this is the place to do so.

[![Webshippers Rate Quotes Configuration](/readme/webshipper_rate_quotes_settings.png)](/readme/webshipper_rate_quotes_settings.png)

*Note:* This will only affect shipping methods shown in checkout and backend, it is not related to `Order` or `Order Line` data within Webshipper. These are two separate functions.

#### Sender Address &amp; Delivery Address

[](#sender-address--delivery-address)

If you want to customize the data being sent to the `Rate Quotes` API in webshipper you can create a custom mapping. By Default we take as much information as possible and send it to Webshipper. But if you have a custom attribute you want to use to filter `Delivery Methods` then add them here.

#### Additional Data

[](#additional-data)

If changing the data on a `Sender` or `Delivery` Address is not enough the `Rate Quotes` object accepts an `Additional Data` field. This field can be used when using `WEL` conditions on your `Rate Quotes` in Webshipper Backend.

[![Webshippers WEL](/readme/webshipper_wel_conditions.png)](/readme/webshipper_wel_conditions.png)

### Order Synchronization

[](#order-synchronization)

The Magento module has a feature to export the orders to Webshipper. This can be done Manually ( via button on order ) or Automatically ( based on order `status` ).

While this module does export the Order to Webshipper the Invoice and Shipments created in Magento are still being triggered via the Magento Rest API from Webshippers Services.

If you wish to handle this behaviour on your own ( if you have your own warehouse integration ), you can disable the automatic Invoice and Shipment creation in Webshippers Admin Panel under `Connect => Order Channels => Edit Order Channel`

### Verify Connection

[](#verify-connection)

In order to ensure the connection to webshipper is setup correctly we recommend using the `Verify Connection` button on the settings page

[![Verify Connection](/readme/webshipper_order_sync_settings_enabled.png)](/readme/webshipper_order_sync_settings_enabled.png)

This button attempts to communicate with Webshipper using the `Configuration Token` setup in an earlier step. It will also attempt to copy the settings setup from the Order Channel ( `transfer_status`, `weight_unit`, `additional_item_attributes`, `additional_order_attributes` )

Upon successful connection you will also see the `Order Channel` has a new banner:

[![Automatic Import Enabled](/readme/webshipper_automatic_import.png)](/readme/webshipper_automatic_import.png)

Known issues:

- No token - if you have not completed the `Configration Token` step, please do so
- Permissions, if you get a 403 HTTP Response it might be because your `Configuration Token` needs to be refreshed, you can refresh it from Webshippers Admin panel under `Connect => Order Channel => Information` and hit the refresh button. Then insert the new `Configuration Token` in Magento following the Step from above

[![Update Configuration Token](/readme/webshipper_update_configuration_token.png)](/readme/webshipper_update_configuration_token.png)

#### Order Status

[](#order-status)

If you want the order to automatically be transfered to Webshipper when an order is created, based on the order's `Status` you can select the status from the multiselect.

[![Order Status Settings](/readme/webshipper_order_sync_settings_enabled.png)](/readme/webshipper_order_sync_settings_enabled.png)

You can select multiple values if you want the order to be exported multiple times. Do note that you can only ship/invoice an order once, if you want a Workflow in Webshipper which automatically processes the order, you need to handle this.

#### Order button ( Manual Transfer )

[](#order-button--manual-transfer-)

If you wish to handle the order export manually, or have an order which is not appearing in your Webshipper backend, you can use this button to debug the issue.

Every time the order is exported a log entry will appear in the Webshipper Log. You can also view the order status history for more details.

### Webshipper Log

[](#webshipper-log)

To ensure clarify between order synchronization we have provided a Log

This contains every order attempted to be sent to webshipper. The status column will append every attempt with a message

[![Webshipper Log Path](/readme/webshipper_logs_path.png)](/readme/webshipper_logs_path.png)

[![Webshipper Logs](/readme/webshipper_logs.png)](/readme/webshipper_logs.png)

#### Order Grid Status

[](#order-grid-status)

You can also view the order's export status from the order grid

[![Webshipper Order Grid Status](/readme/webshipper_order_grid_status.png)](/readme/webshipper_order_grid_status.png)

#### Order Status History

[](#order-status-history)

On the order it self we also provide a history of what has happened

[![Order Status history](/readme/webshipper_order_status_log.png)](/readme/webshipper_order_status_log.png)

If an error occurs with the export you can also find a record of it on the History

[![Order Status history](/readme/webshipper_order_status_error.png)](/readme/webshipper_order_status_error.png)

### Order Settings

[](#order-settings)

In order to adhere to as many setups as possible you can edit almost every aspect of the Webshipper order. The following settings will allow you to modify what data is transmitted. Do note that changing External References on `orders` and `order_lines` can have consequences on how Webshipper will be able to communicate with Magento Rest Api.

[![Order Settings](/readme/webshipper_order_sync_order.png)](/readme/webshipper_order_sync_order.png)

The dropdowns to select `Order Attributes` is each attribute we can find on the Order.

[![Order Attributes](/readme/webshipper_order_sync_order_attributes.png)](/readme/webshipper_order_sync_order_attributes.png)

#### Create Shipment Automatically

[](#create-shipment-automatically)

This setting allows webshipper to create shipments automatically after the order is transmitted. This only applies to webshipper and is not related to a Magento Shipment.

#### Comments ( `external_comment` / `internal_comment` )

[](#comments--external_comment--internal_comment-)

`External Comments` are comments meant for the end user, while `Internal Comments` are meant for internal use. You can use these fields to send messages from Magento backend to your Warehouse.

#### References ( `external_ref` / ´visible\_ref´ )

[](#references--external_ref--visible_ref-)

`External Reference` is a reference used by Webshipper to contact other providers. Changing this will affect features between Magento and Webshipper communication.

`Visible Reference` is the visible reference to the order. This is usually the `Increment Id` and will be visible to anyone in Webshipper and is usually sent as a reference to third party providers like shipping companies. This setting only changes the visual reference to the order\_number not internal API references

#### Additional Data

[](#additional-data-1)

Incase you have some custom data you can add it to your order via Additional Attributes. The list provided at the dropdown is all available Attributes for the order. If you don't see your attribute, ensure it is correctly installed, We attempt to find any and all attributes related to the order, though we do not include custom attributes injected via Model overwrites. Either add your attribute to the order table or add it as an extension attribute.

*Developer note:*The attributes are fetched using `getData()` so if you have a custom overwrite on the `Order` model for a specific attribute you might not see it reflected.

### Order Line Settings

[](#order-line-settings)

Like the `Order` settings you also have the ability to customize how you want each order line to look. Usually `Order Lines` are only treated as a reference but some providers might need a bit more information before they allow a shipment to be created. `Tarif` and `Dangerous Goods` typically used when shipping from country to country. This is handled differently be each Service Provider so ensure your product is updated with the correct information for the given provider

[![Order Line Settings](/readme/webshipper_order_sync_order_line.png)](/readme/webshipper_order_sync_order_line.png)

[![Order Line Attributes](/readme/webshipper_order_sync_order_line_product_attributes.png)](/readme/webshipper_order_sync_order_line_product_attributes.png)

#### Identifier ( `sku` )

[](#identifier--sku-)

The identifier attribute is used to seperate each entity on the order lines, this is usually the `sku` of the product, but if you want to show webshipper a different identifier this is the one to change

#### External Reference ( `item_id` )

[](#external-reference--item_id-)

The `External Reference` is used by external providers incase you have a custom integration with Webshipper. This must be set to `item_id` in order for Webshipper to be able to create shipments in Magento.

#### Description ( `name` )

[](#description--name-)

The `Description` field is used to visually identify the product on the order line. It is the field that customers are most likely to see and when used in combination with `Tarif` it can show border control what kind of product it is.

#### Manufacturer ( `country_of_manufacture` )

[](#manufacturer--country_of_manufacture-)

Some providers require a `Country of Origin` to be passed along, usually as part of a `Tarif` Magento has a built in `country_of_manufacture` attribute by default if you are curious as to how it should be setup.

#### Tarif &amp; Dangerous Goods

[](#tarif--dangerous-goods)

When shipping from country to country you need to be aware of the different taxes applied to each product type. Most countries have an established protocol to identify each product type based on a `Tarif` number. You can use this attribute add a tarif number to your order\_line

`Dangerous Goods` is sometimes required and is a little more complex than a `Tarif` number.

From the Webshipper API Documentation:

```
dangerous_goods_details object
Optional object of key value pairs used for providing information of dangerous goods.
For use with DGOffice, use keys: article_no, package_type_id and packaging_instruction_type.

```

We recommend you store a JSON object on your product with the required information

#### Weight ( `weight` )

[](#weight--weight-)

`Weight` is used by different service providers to determine wether or not they can deliver a package or not. It is also used as part of Taxes and Customs.

Depending on your agreement with your shipping provider you need to send over Weight in their determined `Weight Unit`. We use the `Weight Unit` configured on the `Sales => Delivery Methods => Webshipper`.

#### Additional Data

[](#additional-data-2)

Like the `Order` each `Order Line` also has the ability to send custom data via the `Additional Data` attribute.

*Developer note:*The attributes are fetched using `getData()` so if you have a custom overwrite on the `Product` model for a specific attribute you might not see it reflected.

###  Health Score

40

—

FairBetter than 88% of packages

Maintenance38

Infrequent updates — may be unmaintained

Popularity30

Limited adoption so far

Community16

Small or concentrated contributor base

Maturity62

Established project with proven stability

 Bus Factor1

Top contributor holds 79.5% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~60 days

Recently: every ~164 days

Total

27

Last Release

271d ago

Major Versions

0.8.5 → 1.0.02023-04-11

### Community

Maintainers

![](https://www.gravatar.com/avatar/49bf03a374bb1a2595ce30f5e00bcbfe386c49c32c8d91fa14d7101305c04c3c?d=identicon)[wexo](/maintainers/wexo)

---

Top Contributors

[![WebKenth](https://avatars.githubusercontent.com/u/13419123?v=4)](https://github.com/WebKenth "WebKenth (58 commits)")[![Wexohmor](https://avatars.githubusercontent.com/u/216524401?v=4)](https://github.com/Wexohmor "Wexohmor (9 commits)")[![Tekrus](https://avatars.githubusercontent.com/u/21969475?v=4)](https://github.com/Tekrus "Tekrus (5 commits)")[![wexoks](https://avatars.githubusercontent.com/u/82442712?v=4)](https://github.com/wexoks "wexoks (1 commits)")

### Embed Badge

![Health badge](/badges/wexo-module-webshipper/health.svg)

```
[![Health](https://phpackages.com/badges/wexo-module-webshipper/health.svg)](https://phpackages.com/packages/wexo-module-webshipper)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
