Marketplaces / Lazada / Orders update workflow small tweaks design

Orders update workflow small tweaks design

Current integration and setup at the moment is limited by the fact that we send Invoice number only when sending RTS. This is a no go for any user of seller own fleet because we are updating RTS with their shipping update and for them to ship something they need a generated invoice

This pushes to the change requirement in a few layers

  1. "Set Invoice number" to Lazada needs to be available as flow for either call (whichever is first). Which means if we are doing Packing call at all that's when we need to send the Invoice number, if we are doing only RTD we need to pass the Invoice number with it.
  2. We need to be able to select which flow to pick - directly put order on RFS in our system or keep it at pending till we send a Packing call and only then put it to RFS This is something that should already be done and working but it needs a check as I believe we've never used it
  3. Get Invoice is better to be separated from the Manifest flow as we will have an option to get it prior an RTS call and we want to store a record for Manifest only after RTS. Having in mind how the SOF flow works it will be fine to flag in Orders Lazada a readiness to download and then display the invoice in that same table
Is this article helpful?
0 0 0