• EDI connector (DigitalCAB) generates XML orders in C:\Moneyworks\Orders folder (one order per XML file)
• MW connector (Sussol) reads and. processes XML orders from C:\Moneyworks\Orders folder into MW. Orders successfully imported are moved to processed subfolder.
• MW connector (Sussol) checks for posted invoices in MW which have been modified since the timestamp of the last successful run, and exports XML invoices to C:\Moneyworks\Invoices folder (one XML file per invoice). If successful, update the timestamp (can be manually overridden if needed in MW connector settings).
• EDI connector (DigitalCAB) reads and processes XML invoices from C:\Moneyworks\Invoices folder.
• MW connector (Sussol) generates a log file each time it runs, in C:\MoneyworksConnector\Database\Logs (MW connector is a customised version of http://docs.sussol.net/doku.php/moneyworks:magento_integration).

• The EDI format used by EDI connector contains data for the customer, invoice recipient, buyer and delivery recipient. Currently the buyer is modelled as the customer in MW e.g. “STARK.AA”, where the head office has a code of “STARK.”. For generating invoices, we have to also lookup and export the GLN/EAN for the head office.
• The customer GLN/EAN codes (name.custom1 in MW as name.code has only 11 characters) must be consistent across all systems. When importing an order, MW searches for a match on [Name.Custom1] - import will fail if no match is found.
• The product GTIN codes ([Product.Barcode] in MW = <detail.stockcode> in XML) must be consistent across all systems - importing an order will fail if no match is found. Note also that [Product.Code] (= [Detail.Stockcode]) in MW translates to <detail.supplierarticle> in XML, [Product.Custom1] (=TUN) in MW translates to <detail.manufacturerpart> in XML, and [Product.Custom2] in MW translates to <detail.buyerpart> in XML
• When importing orders, MW uses the account code of 1000 - import will fail if that account code is missing.
• The tax rates and tax codes must be consistent across all systems - import will fail if no match is found.

Script logic:

• When a sales invoice is opened… (on open window or whatever it’s called)
  • IF
    • The customer code starts with: D and
    • The flag field contains “EDI”
    • There is no detail line the the code “RABATEDI” then:
      • Add a detail line that
        • Has the code RABATEDI
        • Has the quantity -1
        • Has a price that is 1% of the total of the other lines (It gives 1% discount on invoices submitted to these customers via EDI

Pick lists are split into 2 sections based on either shoe or accessories. Shoes have their product.category1 set to “Access” - that's it!

1. The number of pairs a customer must order in order to get free shipping is stored in name.custom4
2. As of Friday 04 July 2014 rates are
   1. 1 pair DKK 80,00
   2. 2 pairs DKK 100,00
   3. 3 pairs DKK 100,00
   4. 4 pairs DKK 100,00
   5. 5 pairs DKK 130,00
   6. 6 pairs DKK 130,00
   7. 7 pairs DKK 130,00
   8. 8 pairs DKK 130,00
   9. 9 pairs DKK 130,00
3. So if name.custom4 is “5” and customer orders 4 pairs they pay 100, if they order 5, they pay zero.