Version 3.3.0 - English

6 views
Skip to first unread message

Fraktjakt API

unread,
Jan 22, 2019, 7:16:02 AM1/22/19
to fraktj...@googlegroups.com

Today, Fraktjakt releases a new major improvement to the Fraktjakt API.

The big change we have made is that we introduce a packing algorithm (bin-packing) on the Server side. This means that you in the XML can send in a description of the goods to be shipped instead of which packages to shipped.

Fraktjakt then calculates suitable packages based on Package Templates you can enter in Fraktjakt. In practical terms, this means that you can submit <commodities> tags for each item purchased instead of <parcels> tags.

Previously, the manual had a long chapter for how to suitably calculate the package sizes. It is removed because all this is done on our side now.

We are also aware that some integrations to Fraktjakt send in <parcel> per item that has been purchased in the online store. In order for no one to have to re-encode the integration in order to gain access to the new functionality, we have also introduced a Compatibility Mode. If it is turned on in the Fraktjakt's settings, the <parcel> tags are interpreted as <commodity> tags. In this way, those who have previously submitted a package per purchased item in the online store, don't have to encode their integration. However we naturally recommend that as soon as possible, the correct tags are used.

Sending as few and as small packages as possible is a very good way to lower the shipping costs. Usually you pay not only for the weight of a package, but also for its size. We believe that our packaging algorithm can lower shipping costs for those who use it.


We also recently launched a PHP module for integration with this API. With this we believe that PHP programmers get a much easier job using Fraktjakt.


Other new features of this release is:

* The chapter on how to calculate the package size based on the size of the commodities has been removed, since it is now done server-side in Fraktjakt.

* The ability to specify commodities instead of parcels in the Query API and Order API.

* New chapter on the Commodity element and fewer absolute requirements for the content in the elements.

* The ability to specify Length, Width, and Height in the Commodity element to allow for bin-packing calculations of optimal packages to be used in shipping.

* Other new tags on commodities: in_own_parcel, article_number, shelf_position

* New tag for Query API and Shipment API that overrides the settings for how the search is to be sorted.

* Better error management if you enter an incorrect number in the <shipping_product_id> element in the Order API.

* Less stringent requirements for input data. If certain information is missing, the call is not incorrect, but the missing information can be completed later in Fraktjakt.

* Better support for calls in English.

* Various clarifications.


As usual, you are welcome with all questions and comments.


Best regards

Fraktjakt


Fraktjakt_API_v3.3_en.pdf
Reply all
Reply to author
Forward
0 new messages