Interface to Shipping.NET logistics platform from OnDot.
Current Version: 1.0.6.0as of Business Central 22.
Manual
Creation date: 2024/10/18 The current version of this manual can be found at:
☰ Contents
General
App Ondot ShippingNet Connector Setting up the Ondot Shipping.Net Connector allows a connection between the shipping.net platform and Business Central...
Setup
Extended Setup To guarantee that the shipping processes run efficiently, it is important that all the necessary settings are configured correctly. This includes, among other things, the shipping agent, printer, tariff and shipping costs settings as well as web messages...
Ondot Shipping.Net Printer Setup The printer setup should be able to print shipping labels needed for efficient shipping. Users and their corresponding printer names can be created in the configuration. For example, a user ID such as PSTATION01 can be created, which is associated with the corresponding printer name LStation01...
Shipping Agent Setup The shipping agent setup enables the management of different shipping agents...
OSC Shipping Cost Setup Shipping and packaging costs can be transferred individually to shipping.net using the following table and are not exported as an item line. In this table, the customer can create any number of items as shipping costs. This can be useful for a new shipping method. The shipping costs, if available, are always sent to shipping.net via Web Request, regardless of the item ordered. However, if this is not desired, it can be edited using the Boolean field: Send shipping costs as CustomsAdditionalCostList...
Ondot Shipping.Net Connector Setup
Tariff Setup The implementation of a Tariff setup offers the opportunity to optimize shipping processes according to the individual regulations of the respective destination country and to ensure legally compliant compliance with the valid customs and tax regulations...
Retention Policy A separate retention policy has been provided for the Ondot Shipping.Net Files...
Tasks
Working with the App The process starts with the creation of a sales order in Business Central. A warehouse commission is then created. As soon as this posting is made and the goods have been shipped, the shipment information as well as the customer data, delivery address and contents of the parcel (general. item information, number of Packages, weights,..) are transmitted to shipping.net...
Pages
Ondot Shipping.Net Sales Shipment Colli
Ondot Shipping.Net Shipping Agent Additional Info
Ondot Shipping.Net Files
Ondot Shipping.Net Connector Setup
Page Extensions
Extended Text List On the page Extended Text List the following fields and actions were added...
Extended Text On the page Extended Text the following fields and actions were added...
Inventory Pick On the page Inventory Pick the following fields and actions were added...
Posted Sales Shipment On the page Posted Sales Shipment the following fields and actions were added...
Posted Transfer Shipment On the page Posted Transfer Shipment the following fields and actions were added...
Appendix
Release Notes
Docs / NVXOSC Ondot ShippingNet Connector / General General
Setting up the Ondot Shipping.Net Connector allows a connection between the shipping.net platform and Business Central.
To guarantee that the shipping processes run efficiently, it is important that all the necessary settings are configured correctly. This includes, among other things, the shipping agent, printer, tariff and shipping costs settings as well as web messages.
Various fields such as BusinessPartnerNumber, Tracking Link, Tracking Link as well as standard telephone numbers and follow-up texts can be set up in the main setup. It is also possible to set up automatic sending to shipping.net for sales delivery and warehouse picking.
The field "Standard Proforma Invoice Ending Text" can be used to print a standard proforma post text in the proforma invoice. This is integrated as a standard text code and can therefore be edited at any time.
You can also use "Send Shipping Cost as CustomsAdditionalCostList" to set whether shipping costs should be sent individually in the WebCall.
To check and, if necessary, adjust other various settings, these can be viewed under "Related".
The shipping agent setup enables the management of different shipping agents.
Several settings can be made for shipping.net, which are as follows:
Commercial Invoice Report ID: Specifies the commercial invoice report ID. This report will send to shipping.net as the commercial invoice.
Use AddressLine2: Specifies if the AddressLine1 should be cut at 35 characters and continued at AddressLine2. AddressLine2 will also be cut at 35 characters.
Send Item Prices: Specifies if item prices should be sent.
Send Item Without Sales Price: Specifies if item without sales price should be sent.
Prevent Negative Amounts: Specifies if negative amounts should be prevented. If true negative line amounts will be set to zero.
Active: Shows if the connector is active for this deliverer.
In the AdditionalInfo table, information about the delivery can be added. Depending on which "Additional information" is stored for the delivery agent, this information is also sent. These are provided with abbreviations to simplify the WebCall to shipping.net.
• INV
o AdditionalField1 = Shipping No.
• INVINFO
o AdditionalField1 = Shipping No.
o AdditionalField2 = recipient name
• IOR
o AdditionalField1 = (Post)
• INV2
o Additional information for the Fedex deliverer
• EDT
o Required for printing the label (shipping.net)
The printer setup should be able to print shipping labels needed for efficient shipping. Users and their corresponding printer names can be created in the configuration. For example, a user ID such as PSTATION01 can be created, which is associated with the corresponding printer name LStation01.
The Web Messages setup should be able to transfer shipment tracking data directly to shipping.net automatically to guarantee a seamless communication. The setup offers the possibility to display the payload sent to shipping.net right on the platform. This feature helps ensuring that all relevant data reaches shipping.net and enables successful collaboration between the parties involved.
The implementation of a Tariff setup offers the opportunity to optimize shipping processes according to the individual regulations of the respective destination country and to ensure legally compliant compliance with the valid customs and tax regulations.
The Freight Payer field specifies in the performa invoice who is responsible for the applicable customs duties.
The BusinessPartnerNumber field is input information that is passed on to shipping.net. This can be entered as a default in the "Ondot Shipping.Net Connector Setup" mask. Furthermore, an EORI No. can be provided in the Web Request depending on the country of setup.
The Importer field defines who the invoice is to be sent to, and there are two options for this:
• BusinessPartnerNumber: This field can be filled as required. The customs fee payer is entered as the invoice recipient. If the field is not filled in, the default field BusinessPartnerNumber is used in the "Ondot Shipping.Net Connector Setup" mask.
• Invoice to debtor: This issues the invoice to the customer.
The freight payer field in the Performa invoice indicates who is responsible for the customs fees incurred. This must be entered as a contact.
The EORI No. field is especially useful when shipping to countries outside the EU, where the EORI No. of the following country can be entered in the field. This information is sent to shipping.net as Importer of Record (IOR). If an entry exists in the "EORI no." field in the customer card, this value is transferred to the EORI number text field in the proforma invoice. If there is no entry in the EORI field in the customer card, the EORI number is transferred from the Ondot customs facility for each country.
The Proforma Invoice Ending Text field is printed on the proforma invoice. If a Proforma Invoice Ending Text is available in the Ondot Shipping.Net customs facility, this should be transferred for each country. However, if there is no customs setup, the standard proforma text should be printed in the connector setup.
Shipping and packaging costs can be transferred individually to shipping.net using the following table and are not exported as an item line. In this table, the customer can create any number of items as shipping costs. This can be useful for a new shipping method. The shipping costs, if available, are always sent to shipping.net via Web Request, regardless of the item ordered. However, if this is not desired, it can be edited using the Boolean field: "Send shipping costs as CustomsAdditionalCostList".
The printer setup should be able to print shipping labels needed for efficient shipping. Users and their corresponding printer names can be created in the configuration. For example, a user ID such as PSTATION01 can be created, which is associated with the corresponding printer name LStation01.
The shipping agent setup enables the management of different shipping agents.
Several settings can be made for shipping.net, which are as follows:
Commercial Invoice Report ID: Specifies the commercial invoice report ID. This report will send to shipping.net as the commercial invoice.
Use AddressLine2: Specifies if the AddressLine1 should be cut at 35 characters and continued at AddressLine2. AddressLine2 will also be cut at 35 characters.
Send Item Prices: Specifies if item prices should be sent.
Send Item Without Sales Price: Specifies if item without sales price should be sent.
Prevent Negative Amounts: Specifies if negative amounts should be prevented. If true negative line amounts will be set to zero.
Active: Shows if the connector is active for this deliverer.
In the AdditionalInfo table, information about the delivery can be added. Depending on which "Additional information" is stored for the delivery agent, this information is also sent. These are provided with abbreviations to simplify the WebCall to shipping.net.
• INV
o AdditionalField1 = Shipping No.
• INVINFO
o AdditionalField1 = Shipping No.
o AdditionalField2 = recipient name
• IOR
o AdditionalField1 = (Post)
• INV2
o Additional information for the Fedex deliverer
• EDT
o Required for printing the label (shipping.net)
Fields
Shipping Agent
Specifies the value of the Shipping Agent field.
Shipping Agent Service
Specifies the value of the Shipping Agent Service field.
Description
Specifies the value of the Description field.
Delivery carrier
Specifies the delivery carrier.
Delivery carrier service"
Specifies the delivery carrier service.
Proforma Invoice Report ID
Specifies the proforma invoice report id. This report will sent to shipping.net as the commmercial invoice.
Use AddressLine2
Specifies if the AddressLine1 should be cut at 35 charactes and continued at AddressLine2. AddressLine2 will also be cut at 35 characters.
Send Item Prices
Specifies if item prices should be sent.
Send Item Without Sales Price
Specifies if item without sales price should be sent.
Prevent Negative Amounts
Specifies if negative amounts should be prevented. If true negative line amounts will be set to zero.
Shipping and packaging costs can be transferred individually to shipping.net using the following table and are not exported as an item line. In this table, the customer can create any number of items as shipping costs. This can be useful for a new shipping method. The shipping costs, if available, are always sent to shipping.net via Web Request, regardless of the item ordered. However, if this is not desired, it can be edited using the Boolean field: "Send shipping costs as CustomsAdditionalCostList".
The implementation of a Tariff setup offers the opportunity to optimize shipping processes according to the individual regulations of the respective destination country and to ensure legally compliant compliance with the valid customs and tax regulations.
The Freight Payer field specifies in the performa invoice who is responsible for the applicable customs duties.
The BusinessPartnerNumber field is input information that is passed on to shipping.net. This can be entered as a default in the "Ondot Shipping.Net Connector Setup" mask. Furthermore, an EORI No. can be provided in the Web Request depending on the country of setup.
The Importer field defines who the invoice is to be sent to, and there are two options for this:
• BusinessPartnerNumber: This field can be filled as required. The customs fee payer is entered as the invoice recipient. If the field is not filled in, the default field BusinessPartnerNumber is used in the "Ondot Shipping.Net Connector Setup" mask.
• Invoice to debtor: This issues the invoice to the customer.
The freight payer field in the Performa invoice indicates who is responsible for the customs fees incurred. This must be entered as a contact.
The EORI No. field is especially useful when shipping to countries outside the EU, where the EORI No. of the following country can be entered in the field. This information is sent to shipping.net as Importer of Record (IOR). If an entry exists in the "EORI no." field in the customer card, this value is transferred to the EORI number text field in the proforma invoice. If there is no entry in the EORI field in the customer card, the EORI number is transferred from the Ondot customs facility for each country.
The Proforma Invoice Ending Text field is printed on the proforma invoice. If a Proforma Invoice Ending Text is available in the Ondot Shipping.Net customs facility, this should be transferred for each country. However, if there is no customs setup, the standard proforma text should be printed in the connector setup.
Fields
Country/Region Code
Specifies the value of the Country/Region Code field.
Print Tariff Text
Specifies if the tariff text should be printed on reports
A separate retention policy has been provided for the Ondot Shipping.Net Files.
The suggested value for the retention period is 6 month but it can be adjusted as desired.
Docs / NVXOSC Ondot ShippingNet Connector / Tasks Working with the App
The process starts with the creation of a sales order in Business Central. A warehouse commission is then created. As soon as this posting is made and the goods have been shipped, the shipment information as well as the customer data, delivery address and contents of the parcel (general. item information, number of Packages, weights,..) are transmitted to shipping.net.
If the transfer of the data is not successful, it is possible to submit the data later to shipping.net through the posted sales shipments. It is also possible to create a shipping.net package tracking, in this case the available information is accessed using the web messages and a shipment tracking of the relevant sales shipments is accessed using this information.
Shipment overview
Shipping.net can override the shipment overview for the customer according to individual requirements.
Shipping process can be continued from this point. The shipment is directed to the appropriate shipping service provider, who prepares it for shipment.
Shipping.Net Backend
Within the individual shipments in Shipping.net, the shipment details are once again clearly displayed. Here, among other things, the sender, recipient and the shipping agent of the order in progress can be seen.
Would you like to know what has changed in the extension? Below you'll find an overview of the new features and changes made in the updates.
Build-Overview in DevOps
NVXOSC 1.0.6.0
as of Business Central 22 2024/10/16
Improvements
Added new Field "Send Item Without Sales Price" on Shipping Agent Setup.
Added new Value "Name2" for transfer in WebRequestMgt.
NVXOSC 1.0.5.0
as of Business Central 22 2024/09/24
Corrections
For deliveries with only one parcel, the weight was calculated twice.
NVXOSC 1.0.4.0
as of Business Central 22 2024/06/26
Improvements
Increased dependency on Business Central to BC22.5.
Added a Retention Policy for Ondot Shipping.Net Files.
NVXOSC 1.0.3.0
as of Business Central 20 2024/05/23
Improvements
Lines with quantity 1 are now also distributed evenly across the packages.
The distribution of articles now also works for transfer shipments.
NVXOSC 1.0.2.0
as of Business Central 20 2024/04/19
Improvements
Fixed an error when creating the Recipient block.
NVXOSC 1.0.1.0
as of Business Central 20 2024/04/17
Improvements
The item quantity is now distributed evenly across the packages.
Various fields such as BusinessPartnerNumber, Tracking Link, Tracking Link as well as standard telephone numbers and follow-up texts can be set up in the main setup. It is also possible to set up automatic sending to shipping.net for sales delivery and warehouse picking.
The field "Standard Proforma Invoice Ending Text" can be used to print a standard proforma post text in the proforma invoice. This is integrated as a standard text code and can therefore be edited at any time.
You can also use "Send Shipping Cost as CustomsAdditionalCostList" to set whether shipping costs should be sent individually in the WebCall.
To check and, if necessary, adjust other various settings, these can be viewed under "Related".
Several settings can be made for shipping.net, which are as follows:
Commercial Invoice Report ID: Specifies the commercial invoice report ID. This report will send to shipping.net as the commercial invoice.
Use AddressLine2: Specifies if the AddressLine1 should be cut at 35 characters and continued at AddressLine2. AddressLine2 will also be cut at 35 characters.
Send Item Prices: Specifies if item prices should be sent.
Send Item Without Sales Price: Specifies if item without sales price should be sent.
Prevent Negative Amounts: Specifies if negative amounts should be prevented. If true negative line amounts will be set to zero.
Active: Shows if the connector is active for this deliverer.
In the AdditionalInfo table, information about the delivery can be added. Depending on which "Additional information" is stored for the delivery agent, this information is also sent. These are provided with abbreviations to simplify the WebCall to shipping.net.
• INV
o AdditionalField1 = Shipping No.
• INVINFO
o AdditionalField1 = Shipping No.
o AdditionalField2 = recipient name
• IOR
o AdditionalField1 = (Post)
• INV2
o Additional information for the Fedex deliverer
• EDT
o Required for printing the label (shipping.net)
The Importer field defines who the invoice is to be sent to, and there are two options for this:
• BusinessPartnerNumber: This field can be filled as required. The customs fee payer is entered as the invoice recipient. If the field is not filled in, the default field BusinessPartnerNumber is used in the "Ondot Shipping.Net Connector Setup" mask.
• Invoice to debtor: This issues the invoice to the customer.
The freight payer field in the Performa invoice indicates who is responsible for the customs fees incurred. This must be entered as a contact.
The EORI No. field is especially useful when shipping to countries outside the EU, where the EORI No. of the following country can be entered in the field. This information is sent to shipping.net as Importer of Record (IOR). If an entry exists in the "EORI no." field in the customer card, this value is transferred to the EORI number text field in the proforma invoice. If there is no entry in the EORI field in the customer card, the EORI number is transferred from the Ondot customs facility for each country.
The Proforma Invoice Ending Text field is printed on the proforma invoice. If a Proforma Invoice Ending Text is available in the Ondot Shipping.Net customs facility, this should be transferred for each country. However, if there is no customs setup, the standard proforma text should be printed in the connector setup.
Shipping process can be continued from this point. The shipment is directed to the appropriate shipping service provider, who prepares it for shipment.
Within the individual shipments in Shipping.net, the shipment details are once again clearly displayed. Here, among other things, the sender, recipient and the shipping agent of the order in progress can be seen.
