Myer Inbound (Orders)

The purpose of this document is to detail the Orders communication for Myer through IPT Systems.

Expectations are the following:

1. Once we receive an order there won’t be any additional changes to it
2. Once we’ve received an order we treat it as a Ready for Shipping order regarding payments and everything
3. Any Refunds/Returns are done within Myer and we don’t receive any updates on that
4. Communication in Myer is done via EAN so we have to map to our SKU

Below can be found an example file and its mapping in Hemisphere

Example file:

{
  "order_number": "CC4500624308D000",
  "oms_order_number": "1501369596",
  "datetime": "202005270025",
  "shipto_first_name": "Elvira Kiss",
  "shipto_last_name": "",
  "shipto_address_1": "8 Victory Ct",
  "shipto_address_2": "",
  "shipto_suburb": "BRIGHTON EAST",
  "shipto_state": "VIC",
  "shipto_post_code": "3187",
  "shipto_country": "AU",
  "shipto_email": "el.mi@bigpond.com",
  "shipto_mobile": "+610402892317",
  "purchasing_first_name": "Elvira Kiss",
  "purchasing_last_name": "",
  "order_inc_gst": 299.0020,
  "OrderType": "PO",
  "items_purchased": [
    {
      "barcode": "5025155041406",
      "buyer_code": "690131890",
      "description": "Dyson 282064-01 V7 Trigger Handheld Vac",
      "unit_inc_gst": 299.0020,
      "ordered_qty": 1,
      "gift_card": "N",
      "gift_wrap": "N"
    }
  ]
}

Mapping:

Based on the above and expectations on how we are to receive the orders we need to follow the below actions:

1. Every new order should be stored as “waiting_for_delivery” Hemisphere tool_status when created
2. In case we read an existing order a second time we are to skip it and simply store an error on the original order so it can be manually checked what is happening
3. The Marketplace status of the order (as it is not provided) should reflect our own status
4. In case of crucial information missing we should mark the order as “Incomplete”. Crucial information is treated as below:
   1. Any of the shipping address fields (excluding shipping street 2 address)
   2. Ship to Name
   3. Order total
   4. Item Barcode
   5. Item Quantity
   6. Item Price
5. In case we can’t map the SKU via EAN or a Barcode from “item” we treat the order again as “incomplete” and store the relevant error for the missing information
6. We need to create the order payment record with the total being the paid sum, the transaction ID being the same as the Marketplace order ID and the date the same as the order created time
7. We are to create Order Item Line records directly as we consume the order as even if it goes to incomplete we are more likely to not receive a new file with any fixes than actually getting something again (which we will not read based on the validations from above). These lines should all have a status “created” to be able to further differentiate them for any next steps. Only cases where we can’t create order_item_lines is if “item_quantity” is missing or the whole item section is not populated from the payload
8. We are to check the products of OOS and mark them if 1) they don’t have enough quantity to fulfil what is requested in the order or 2) we can’t find such a product / product item at all
9. We have to fill in the Subtotal of an order to be the same as the total and the Currency to always be “AUD”