Linnworks integrates with different types of e-commerce solutions. There are two ways of linking up the order management systems with your websites
The direct integration Linnworks will be able to talk to your e-commerce site directly - download orders, update status of the order, submit fulfillment data and update stock levels every time you synchronize. Whereas CSV data import/export is means of interfacing with your e-commerce site if complete integration is not needed or not available. Generally speaking if you own your e-commerce site and have access to its scripts, you can do direct integration either by re-using already written templates for interfacing, create your own one or commissioning bespoke written templates.
By default we have many ready to use templates for most common e-commerce solutions such as osCommerce, Magento, ZenCart, JSHOP etc.
Download available website integration templates
First of all, make sure you know (or have access to) the following information in order to install interfacing scripts
If you are installing the integration script from template (already written script)
If you can't find already created template for your type of e-commerce website, you can create your own integration definition. In order to do that you need to know the database schema that drives your e-commerce website. If you are not confident you know the schema well enough to create the integration template ask your web designer or contact us we are more than happy to help us.
GetNewOrdersQuery – SQL statement to retrieve new orders from the server. The set of orders will be retrieved every time you synchronize. Order Reference is the uniqueidentifier for the order, if the order already with the OrderReference already on the system it will be ignored without attempting to overwrite or update information. The query requires the following fields to be returned (matching the column names exactly, case sensitive)
orderID - order id on the web (this will not get imported into the linnworks, it is only used to update the status of the order after it has been downloaded. And also to relate this order to order items.
shippingTotal
dReceievedDate
fTotalCharge
fTax
cCurrency
PostalServiceTag – postage service tag which will be matched to Postage Service Tag in linnworks
ReferenceNum - Order Reference number. This is the reference number by which the order will be updated after it has been processed (dispatched). THIS REFERENCE NUMBER SHOULD BE UNIQUE FOR LINNWORKS. MAKE SURE YOU MAKE IT UNIQUE FOR ALL INTEGRATED SYSTEM. Good practice is to add some sort of identifier to separate the reference number from all other integrated sources. For example if your order reference is simply autoincremented number (1,2,3 ...n) it might clash with order imported from other sources. To make it unique simply add something at the beginning of the order reference like 'MYWEB'+orderid to make reference number MYWEB1,MYWEB2, ... MYWEBn
cFullName
cShippingAddress - shipping address as will appear on the postage label or an invoice. If you don't store it in the database as a single field text value. Use addCompany, addName and leave cShippingAddress blank. When the system imports data it will make cShippingAddress field from these columns while properly formating it to make an address
cPostCode
Country
cEmailAddress
PackagingGroup
addCompany - additional fields to make up shipping address
addName - additional fields to make up shipping address
addAddress1 - additional fields to make up shipping address
addAddress2 - additional fields to make up shipping address
addTown - additional fields to make up shipping address
addCounty - additional fields to make up shipping address
addCountry - additional fields to make up shipping address
addPostcode - additional fields to make up shipping address
GetOrderItemQuery – this SQL statement is executed against your database everytime you synchronize. It will be executed in conjunction with GetNewOrdersQuery where first can be seen as Order Header and second is Order Lines
orderid - order id, this should match order id in GetNewOrdersQuery
ItemNumber - item number as in linnworks (if item does not exists it will be created)
Quantity - quantity of products purchased
CostPerUnit – cost per product (not the total cost per order line)
ItemTitle – item title
MarkAsDownloadedOrders – once the order has been downloaded and order created in linnworks, you need to mark this order as downloaded on your website database to avoid redownloading it next time. This is done by issuing some sort of update statement to update status field of an order to state downloaded. The query take in a parameter [{orderid}]. The query will be executed for every downloaded order. Query example
updateMarkAsProcessedOrders – once an order has been processed, ideally you need to mark it on the web as despatched/processed. The query will be executed for every website downloaded order. The query takes two parameters [{dProcessedOn}] and [{OrderReference}]. For example,
order_header
set `status` = 8
where orderid = [{orderid}]
UPDATE
order_header
set
`status` = 6,
process_date = '[{dProcessedOn}]'
where orderreference = '[{OrderReference}]'
UpdateStockLevel – the query will get executed for every changed stock level in linnworks and for every item currently in open orders. The quer takes in two parameters [{Level_LessOrderBook}] and [{ItemNumber}]
update products
set
stockLevel=[{Level_LessOrderBook}]
where ItemNumber = '[{ItemNumber}]'
We completely understand that the integration with the website requires some technical knowledge and understanding of your website database. If you need any help integrating your website in linnworks we offer help free of charge for premium license holders. If you are evaluation the system you can get answers from our technical support. Please use contact form to submit your query or post the question on the forum
| GOTO |
|
Linnworks Downloads Documentation Training Videos News and Updates Submit support ticket Product Enquiry Purchase License Subscribe for license |
| Chat to Sales Rep |
|
|
