Often, sellers take advantage of coupon codes, sales, etc and may buy the same MSKU at different prices even on the same day.
For example, on Friday you purchased 10 widgets for $10 each. On Saturday you bought 10 more widgets for $8 each because you had a coupon. On Monday you try to put all of these widgets in the same batch, but List will only allow you to enter one cost. This is when the Replenishments process comes into play. While listing, just choose one of the cost/units. Then, once the product feeds have been sent follow the process outlined below.
This process also applies if you need to enter multiple cost/units for items that were not listed through InventoryLab. If you do not separate your MSKUs into replenishments, InventoryLab will use the first Cost/Unit we collected as the COGS information for accounting purposes.
Creating Replenishments Using Add Row
Splitting Quantities to Create Replenishments
Creating Replenishments Using Add Row
Navigate to the Inventory > FBA/Merchant tab and do a search for the item. When the item appears in the search results, click on the MSKU as shown below.
Click on the Add Row button.
Type in the 4 pieces of information and click the Create New Replenishment Row button.
Your MSKU will then be split into replenishments as shown in this example. Each Replenishment will be a new number.
If you then add another row to the same MSKU, you will see the data pre-filled from the row you had just added for easy entering new info on that same MSKU. .
If you move to a different MSKU, you will see the data is not pre-filled to prevent errors.
Splitting Quantities to Create Replenishments
If you want to create replenishments with the inventory already showing in a replenishment row, you can split it.
Click on the Split icon next to the item.
A pop-up will appear where you can enter the information for the next purchase. If you need to add more, click Split Again. When you're finished, click Complete Split.
The correct accounting information will show for all items.
0 comments
Article is closed for comments.