Upload stock levels to Neto
Overview
Find out how to configure your Neto integration’s stock settings and keep your Neto stock levels up to date.
The stock level of a product is the number of available units.
It’s essential to regularly upload your Cin7 Omni stock levels to Neto. If you don’t upload stock levels after purchasing goods, you could understock goods in Neto and lose sales. And if you don’t upload your stock levels after making sales via other channels, you could oversell inventory and damage your reputation.
You should update your Neto stock levels whenever your Omni and Neto stock levels get out of sync, which includes:
After you receive stock
After you fulfill non-Neto sales orders
After you download Neto sales orders
Before updating your Neto stock levels, you must choose which Omni branches to upload stock levels from and how to have your Neto stock levels calculated.
Omni only uploads the stock levels of products mapped to Neto. Virtual stock levels of bill-of-material (BOM) products, and stock levels of products with units of measure (UOM), are uploaded too.
Configure upload stock levels
1. Configure branches
Omni products may have stock at multiple branches. So you must decide whether to upload the total amount of stock from across your Omni branches, or whether to upload stock levels from selected branches only.
Log in to Cin7 Omni.
From the Integrations menu in the navigation, open your Neto integration.
Open Settings.
Open the Settings tab.
Ensure Stock is turned on.
-
Under Stock, either:
To upload the total amount of stock from all branches, set Get Stock Levels From to All Branches.
To upload stock levels from selected branches, set Get Stock Levels From to Selected Branches and then select those branches.
Select Save Settings.
2. Configure calculation
In your Neto integration settings, use Type of Stock Level To Use on Neto to choose how your products’ stock levels are calculated for Neto. For a description of each option, see Neto settings.
Optionally, you can also use Set Buffer Stock to have a fixed quantity automatically subtracted from your Neto stock levels.
For example, say you have set Type of Stock Level To Use on Neto to Stock on Hand and have 100 units of stock on hand. If you’ve set Set Buffer Stock to 20, that product’s Neto stock level will become 80 (that’s 100 minus 20).
Update stock levels
There are two ways of uploading stock levels to Neto:
Log in to Cin7 Omni.
From the Integrations menu in the navigation, open your Neto integration.
-
On the Stock Update Status tile, select either:
Update All Stock, to upload the current stock levels of all mapped Omni products
Update Recent Modified Stock Levels, to upload the stock levels of mapped Omni products whose stock levels have changed since you last uploaded stock levels
Most of the time, you’ll only have to run Update Recent Modified Stock Levels, which executes more quickly. However, whenever you reconfigure how stock levels upload, you’ll need to run Update All Stock once.
Automatically update stock levels
Update Recent Modified Stock Levels runs automatically every time you open your Neto integration dashboard. It also runs automatically after downloading Neto sales orders if you’ve enabled Auto-Sync Stock in your Neto integration settings.
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB