What happens on duplicate Create requests with the same master data and sku attribute? (Applicable to all type of masters, SKU Attributes)
The calls made for creation of product masters are idempotent meaning that if duplicate requests are sent, no change will be made. Therefore, if the product master data was successfully saved after the first call, subsequent duplicate calls will have no impact on the data. Each duplicate call will result in a 200-OK response.
What happens on duplicate Requests with the same master data and different sku attribute? (Applicable to all type of masters,SKU Attributes)
If different attribute data is passed for a specific product master using the create-article-master API endpoint, the SKU attributes will not be updated to the latest passed value.
However, when using the add-or-update-SKU-attributes API endpoint, the SKU Attribute Data from the latest successful call will be saved for the specified product master, i.e. the SKU attributes will be updated.
What if ERP is not able to send Tax code?
Increff WMS is a WMS module, hence Clients should never rely on Increff WMS to compute accurate taxation. This is ERP’s responsibility. So in case ERP is not able to send correct tax code for each sku, it can use a default value GIVEN that in such case Increff Omni tax computation will never be used.
What if ERP is capable of sending the tax breakup ?
During packing, the Increff Omni system can fetch the tax breakup from Order Source.
What if ERP is not able to send the Image URL?
The image URL is not a mandatory field and it may be left blank.
If the image URL is absent or incorrect, the image of the product won’t be displayed on WMS screens. This will affect picking, packing and all QC related operations.
Image URLS can also be updated using the product data updation API or from Increff OMS UI.
Note: The image URL must be a string under 255 characters
How to update an existing SKU master?
The SKU Masters can be updated using the updateArticleMaster endpoint (assuming that the listing for that product is present). OR Product master can also be updated from Increff OMS UI.
Can ERP create marketplace listing/mapping using OmniMagic2?
No, this feature is not available at the moment.
Why is there a batching of calls? What scenario requires batching ?
It is an industry standard to use batching wherever possible.
This reduces no. of calls,
Improves scalability
We try to build things for scale. Imagine receiving 10000 orders per hour. If we sequentially respond to every single order, and one call takes 100 ms, then without batching it would take a long time to send acks for all orders.
This in turn can result in your order processing pipelines to get delayed (e.g. sending confirmation mails to customers, booking AWB nos. etc)
Companies like Amazon also follow the same mechanism for their EDI integrations and we've followed the best industry practice over here"
How to get available to sell inventory from Search Inventory calls
Why is the batch processing accumulated if one batch fails and why subsequent batches are not processed?
If we cannot trust a system for 1 batch then it cannot be trusted for other batches also. The simple reason is that there are no guarantees that subsequent batches won't fail. If one cannot give a guarantee, then effectively, we are asking a computer system to keep trying other batches and "hopefully" some of them will succeed.
Such a system would also be complex to develop. There would be many considerations to make:
What strategy would be used to retry the failed batch? Exponential backoff, fixed delay, fixed rate?
How long (hours, days) should the system keep retrying for a failed batch ?
What happens when there are too many failed batches? Because, eventually you would reach a point where you have too many failed batches, and those batches would themselves become a bottleneck for "good" batches. Because retrying for bad batches would delay good batches.
What happens if we stop retrying after 2-3 days, and then you fix the system at your end? How do you develop a mechanism to re-activate those batches? How do you develop a mechanism to authorize retries of such batches? Who will authorize it ? Client or Increff? How do you automate such a process?
How would you develop a "measure" of success of this mechanism? Is < 1% batch failure rate acceptable? 0.1% etc.