Imports Glossary
- 03 May 2023
- 3 Minutes to read
- DarkLight
Imports Glossary
- Updated on 03 May 2023
- 3 Minutes to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
All the columns for each of the imports files we make available on the Admin Panel are detailed below. We let you know the format we need for smooth and error-free imports, as well as whether or not the column is required or optional.
Asset
Column | Details | Format | Required/Optional |
---|---|---|---|
Location | Location where the asset is available. | Must be an exact match (spelling and case) with the relevant location in your Nexudus account. | Required |
Name | Name of the asset. | Assets can share the same name as long as they all have a unique SKU. | Required |
Description | Description of the asset. | — | Optional |
SKU | Stock keeping unit of the asset. | Must be unique to each asset. | Required only if multiple assets share the same Name. |
Value | Estimated value of the asset. This is just a guideline should you need to charge the customer for damage or loss. | — | Optional |
CoworkerId | ID of the customer assigned the asset. | — | Optional |
CoworkerEmail | Email of the customer assigmed the asset. | — | Required if you fill out CoworkerNotes, CoworkerAssignedFrom, or CoworkerAssignedTo. |
CoworkerNotes | Notes you want to link to the asset assigned to a customer. | — | Optional, but you must fill out CoworkerEmail and CoworkerAssignedFrom to import this column. |
CoworkerAssignedFrom | Date when the asset was assigned to the customer. | yyyy-mm-dd hh:mm | Required if you fill out CoworkerEmail or CoworkerNote. |
CoworkerAssignedTo | Date when the asset was returned by the customer. | yyyy-mm-dd hh:mm | Optional |
Products
This file lets you import products to your Nexudus Inventory.
Column | Details | Format | Required/Optional |
---|---|---|---|
Location | Location where the product is available. | Must be an exact match (spelling and case) with the relevant location in your Nexudus account. | Required |
Name | Name of the product. | — | Required |
DisplayOrder | Display order of the product on the Members Portal. | Use 10 or 100 increments to make it easier to order new products later. For example, product 1 - 100 , product 2 - 200, product 3 - 300, etc. | Optional |
Description | Description fo the product displayed on the Admin Panel and the Members Portal. | — | Optional |
Price | Price of the product per unit. | — | Required |
Tags | Tags that can be used to filter products on the Admin Panel and the Members Portal. | Must be an exact match (spelling and case) for all products sharing the tag. | Optional |
SKU | Stock keeping unit of the product. | Must be unique to each product | Optional |
Visible | Make the product visible on the Members Portal for customers to purchase. | YES or NO | Required |
Availability | Make the product only purchasable as a one-off or both as a one-off and on a recurring basis. | OnlyOneOff or RecurrentOrOneOff | Required |
Product sales
This files lets you import product sales and add them to customer acconts in Nexudus.
You must import your products and customers or create them directly on the Admin Panel before importing product sales.
Column | Details | Format | Required/Optional |
---|---|---|---|
Location | Location where the product is sold to a customer. | Must be an exact match (spelling and case) with the relevant location in your Nexudus account. | Required |
Email of the customer that should be invoiced for the product purchase. | Must be an exact match with the email of an existing customer in your Nexudus account. | Required | |
ProductName | Name of the product. | Must be an exact match (spelling and case) with an exisiting product in your location's Inventory. | Required |
RegularCharge | Charge the customer for the product every time their main contract is renewed. For contacts, the product is sold every time an invoice is raised. | YES or NO - if you say YES, the product sold must also be available as a recurrent product. | Required |
Quantity | Niumber of units of the product sold to the customer. | — | Required |
Price | Price of the product per unit. This price can be different from the product's price on the Admin Panel. | — | Required |
ActivateNow | Release the benefits linked to the product as soon as the product is added to the customer's account, whether or not they've paid for it. | YES or NO | Required |
DueDate | Date when the customer's first invoice for the product becomes due. | yyyy-mm-dd hh:mm | Required |
InvoiceOn | Date when you first want to invoice the customer for the product. | yyyy-mm-dd hh:mm | Required |
RepeatUntil | Date until when the product should be invoiced. | yyyy-mm-dd hh:mm | Required |
InvoiceThisCustomer | Invoice the customer for the purchase instead of their team's paying customer. | YES or NO | Required |
Subscribers
This import file lets you import newsletter subscribers.
Column | Details | Format | Required/Optional |
---|---|---|---|
FullName | First and last name of the subscriber. | — | Required |
CompanyName | Name of the subscriber company. | — | Optional |
Reason | Source that brought the subscriber. | — | Optional |
Email address of the subscriber. | — | Required | |
Group | Subscriber group the subscriber belongs to. | Must be an exact match (spelling and case) with an existing subscriber group in your Nexudus account. | Optional |
Event attendees
Column | Details | Format | Required/Optional |
---|---|---|---|
CoworkerEmail | Email of the customer attending the event. | — | Required if no AttendeeEmail |
CoworkerName | Name of the customer attending the event. | — | Required if no AttendeeName |
AttendeeEmail | Name of the person attending the event. | — | Required if no CoworkerEmail |
AttendeeName | Name of the person attending the event. | — | Required if no CoworkerName |
EventName | Name of the event. | Must be an exact match (spelling and case) with an existing event in your Nexudus account. | Required |
EventProductName | Name of the event tickets being purchased. | Must be an exact match (spelling and case) with an existing ticket type in your Nexudus account. | Required |
PurchaseOrder | Purchase order number of the customer, if any. | — | Optional |
DueDate | Date when the invoice for the event ticket should become due. | yyyy-mm-dd hh:mm | Optional |
Was this article helpful?