Import credit notes
Overview
You can import new credit notes into Cin7 Omni from a spreadsheet by:
Uploading the spreadsheet data into Cin7 Omni.
Mapping spreadsheet columns to Cin7 Omni fields.
Importing credit notes.
Download and edit template
You can download the credit notes import template. You can edit the spreadsheet and add your new credit note information.
Upload spreadsheet data into Cin7 Omni
After you have added your credit note information to the spreadsheet, you can import into Cin7 Omni.
In the navigation, select
Sales and then Credit Notes.
Select Actions and select Import Credit Notes. You will need to have an existing credit note to see the Actions menu.
-
You can then import your credit notes by selecting either:
-
Import from file upload
Cin7 Omni will import the data from the uploaded spreadsheet.Select Choose file and then select your .csv spreadsheet.
Select Next Step.
-
-
Or Copy and paste file from clipboard
You can copy and paste the data from a spreadsheet. Cin7 Omni will then import what you have pasted.Copy your spreadsheet data and paste it into the field.
Select Next Step.
Map spreadsheet columns to Cin7 Omni fields
Cin7 Omni will suggest fields that match your spreadsheet columns.
If the Cin7 Field is blank, or mapped to the wrong field, click on the Cin7 Field dropdown and choose the field you want to update.
Select Next Step.
Import credit notes
Select Import New Credit Notes to import your new contacts into Cin7 Omni.
A green success message will display when importing data is successful.
Click Finish, Back to Credit Notes to return to your list of credit notes.
- 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