Acumatica warranty SKUs

Add the SureBright warranty catalog to Acumatica Cloud ERP as non-stock items from the plan SKU CSV in the Merchant Portal, then let your existing Acumatica to Shopify connector publish them.

Works onShopify

Use this page when you run Acumatica Cloud ERP and sell SureBright plans through a Shopify store connected to it. You download the warranty products and their prices from the Merchant Portal as a CSV (see Download your plan SKUs), or SureBright sends you a ready-to-import sheet. You load that file into Acumatica once. From then on the warranty SKUs live in your catalog and publish to Shopify like any other product, and online warranty sales flow back into Acumatica automatically.

This procedure was validated against Acumatica Cloud ERP 2026 R1 (build 26.100.0175). Screen IDs are stable across versions and can be typed into the search box; field labels and layouts vary slightly.

Who does what#

StepWhoWhat happens
1. Gets the SKU CSVYou, or SureBrightProducts > Download plan SKUs in the Merchant Portal, then add an ItemClass column holding your class ID on every row. Or ask SureBright for the ready-to-import sheet, which already has it.
2. Prepares the instanceYou, onceRaise the inventory ID length, then create the item class SB-PRODUCT.
3. Imports the CSVYouThe SKUs become non-stock items in Acumatica.
4. Publishes to ShopifyAutomaticThrough your existing Acumatica commerce connector.

Everything you add is standard: non-stock items and one item class, created with Acumatica's built-in import tools. No existing configuration, workflow, chart of accounts or data is changed, and any SKU can be deactivated at any time. The one exception is the segmented key length in the first action, which is tenant-wide; route that change through whoever owns your Acumatica configuration.

Agree two values with SureBright first#

ValueDefaultWhy it matters
Item class nameSB-PRODUCTIt is the value in the CSV's ItemClass column, and it must match the class you create character for character, including the hyphen. If your organisation requires a different name, agree it before the sheet is issued rather than editing the file.
Inventory ID (SKU) formatSBW-1U-CEAD-49999SBW (SureBright Warranty), term and region (1U = 1 year, USA), coverage code (CEAD = Consumer Electronics, Accidental Damage), and the upper price of the band in cents with no decimal. 17 characters. The same SKU must appear in Acumatica, in Shopify and on the warranty line of each online order, or online sales will not reconcile. A shorter convention is possible; tell SureBright and the sheet is adjusted.

By default the sheet comes in the minimal format (InventoryID, Description, ItemClass, BasePrice) and relies on the item class for everything else. A full-details sheet with every Acumatica field spelled out is available on request once you have confirmed UOM, tax, posting class and GL codes with SureBright.

csv
InventoryID,Description,ItemClass,BasePrice
SBW-1U-CEAD-04999,"CE Accidental Damage · 1yr · ≤ $49.99",SB-PRODUCT,4.99
SBW-1U-CEAD-09999,"CE Accidental Damage · 1yr · $50–$99.99",SB-PRODUCT,8.99
SBW-1U-CEAD-24999,"CE Accidental Damage · 1yr · $100–$249.99",SB-PRODUCT,14.99
SBW-1U-CEAD-49999,"CE Accidental Damage · 1yr · $250–$499.99",SB-PRODUCT,24.99

The descriptions contain characters that US-ASCII cannot represent, so the data provider's encoding must be set to UTF-8 (see Action 2).

Set up Acumatica in three actions#

Do them in this order. The first two are hard dependencies of the third.

Action 0: raise the segmented key length (CS202000)#

Acumatica builds inventory IDs from a segmented key named INVENTORY, which ships with a length of 10 characters. A warranty SKU is 17. Acumatica does not reject the longer value; it truncates it silently and the import still reports success. Distinct SKUs collapse onto a handful of surviving codes, each overwritten by the next row that truncates to the same string.

This is the only failure in the procedure that raises no error, and re-importing afterwards does not repair the damaged records. If an import has already run under the old limit, remove or deactivate the truncated items before re-running.

  1. Open CS202000, Segmented Keys

    In Segmented Key ID select INVENTORY.

  2. Change the segment length

    In the segment grid change Length from 10 to 20. Leave Validate, Align and Editable alone; 30 is the maximum Acumatica allows. The length is a maximum, not a fixed width: shorter codes are stored exactly as entered.

  3. Save, then log out and log back in

    Acumatica caches the key definition per session. Until you sign in again the field keeps truncating at 10 characters without notice.

  4. Confirm the change took effect

    Open IN202000 and type a full 17-character SKU into Inventory ID. If the whole string stays in the field the change is active; if it stops accepting characters part-way, sign out and in again.

Raising the length is additive and leaves existing items untouched. Lowering it later is not safe: it can orphan codes that no longer fit.

Action 1: create the warranty item class (IN201000)#

The class sets item type, unit, GL accounts and tax once, so every warranty SKU inherits them. Create it before importing or every row fails with no accounting treatment.

Two prerequisites on a new tenant: a tax category must exist (TX205500), because Acumatica will not save any non-stock item without one and a new tenant has none; and TX205500 itself needs company and branch setup (CS101500 / CS102000) to open.

Field (IN201000)Set toNotes
Class IDSB-PRODUCTMust match the CSV's ItemClass value exactly.
DescriptionSureBright Product ProtectionFree text.
Item TypeNon-Stock ItemA warranty has no inventory to track.
Stock Itemcleared
Base / Sales / Purchase UnitEAVerify the unit exists in your Units of Measure list; the field accepting input is not confirmation.
Require Shipment, Require ReceiptclearedNothing to pick, pack or receive.
KitNo
Export to External Application (eCommerce)enabledPuts every imported SKU into the Shopify sync. Makes Description mandatory on each item; SureBright's sheet carries one for every row. Labelled Export to External System in some builds.
Posting Classyour choice, for example NONSTOCKSet with your accountant.
Sales / Income Accountyour choice, for example a dedicated Warranty Income accountKeeps warranty revenue separately reportable.
Deferral Codeyour choice, usually None
Accrue Cost, Expense / COGS Accountyour choice, usually offOnly needed if you book a per-sale payable at point of sale.
Tax Categoryyour choice, must existThe category your tax configuration applies to service and warranty lines.

Create a dedicated class rather than reusing an existing one: an existing class may carry a different base unit, which then propagates silently to every warranty SKU.

If these instructions do not match your system#

Your Acumatica may already have its own item-class scheme, a naming rule for classes, or a class name in an older SureBright sheet that differs from the one here (for example SB_PRODUCT_PROTECTION). You do not have to follow the default name.

Your situationWhat to do
Your organisation names item classes its own wayCreate the warranty class under your name, with the settings in the table above. Tell SureBright the exact Class ID, and the sheet is reissued with that value in the ItemClass column.
You want to use a non-stock class you already haveCheck it against every row of the table above, especially Item Type, Base / Sales / Purchase Unit, Require Shipment and Export to External Application. If they all match, tell SureBright its Class ID. If any differ, create a dedicated class instead.
Your sheet names a class that does not exist in your systemDo not edit the file. Ask SureBright to reissue the sheet with the class you created.
A screen or field in this guide looks different in your buildSend SureBright the screen ID, a screenshot and your Acumatica version.

Whatever the class is called, the ItemClass value in the sheet must match its Class ID character for character.

Action 2: import the CSV#

  1. Create a data provider (SM206015)

    Enter a Name (for example Warranty SKU Import) and set Provider Type to CSV Provider, then Save. Only after saving does the FILES link in the top-right corner become available: use it to upload the CSV; the FileName parameter fills in on its own. On the PARAMETERS tab change Encoding from US-ASCII to Unicode (UTF-8) and save again.

  2. Fill the schema

    On the SCHEMA tab click Fill Schema Fields in the Source Fields panel; the four columns appear, all typed String. Change BasePrice to Decimal (re-running Fill Schema Fields resets it). Tick Active on the source object in the Source Objects panel; it is clear by default and the import scenario will not list the object until it is ticked. Save.

  3. Build the import scenario (SM206025)

    Set Screen Name to Non-Stock Items (IN202000), Data Provider to the one you created, and Provider Object to your CSV object. If Provider Object is empty and outlined red, go back and tick Active on the schema tab. Toggle Show All Commands to see the service rows Acumatica writes for you; they cannot be deleted.

  4. Map the four columns

    Pick each target from the magnifier lookup rather than typing it; typed text sets only half the value and Save fails with 'Target Object' cannot be empty. Type the plain column name (InventoryID), not the =[InventoryID] formula form.

    Field on IN202000TargetSource field
    Inventory IDItem.InventoryCDInventoryID
    Item ClassItemSettings.ItemClassIDItemClass
    Default PriceItemCurySettings.BasePriceBasePrice
    DescriptionItem.DescrDescription

    To confirm a target, open the form with View Screen, hold Ctrl + Alt and click the field; the Element Properties dialog shows the data view and field name. The object names ItemSummary and PriceGL found in some older notes do not exist.

  5. Add the Save row

    Add <Action: Save> as the last row with Execute Action set to Once, for Last Detail. Without it every row stages and nothing commits; the run fails with 12 items have not been processed successfully. View name: Item. and the history shows Processed: 0 records.

  6. Run the import (SM206036)

    Select the scenario, tick Discard Previous Result, click Prepare and scan for red error rows, then click Process. Tick Discard Previous Result on every re-run or Prepare reuses the previously staged rows.

Verify the import (IN202000)#

Open Non-Stock Items and search the prefix SBW. Each item should show the correct item class, price and Active status, and the Inventory ID should carry all 17 characters. Then count: the number of records must equal the number of rows in the sheet. Processing completed successfully is also what a truncated import reports, so the record count is the only reliable check. Three records where there should be twelve, with IDs like SBW-1U-CEA, means Action 0 was skipped: complete it, remove the affected items and re-import.

Check the SKUs publish to Shopify#

Publishing is automatic through your existing Acumatica commerce connector; there is nothing to set up or schedule. Because the item class enables Export to External Application, every imported SKU is already in the sync. Confirm two things once:

WhereSettingExpected
Item, eCommerce tab (IN202000)Export to External Application / Availability / VisibilityEnabled / Available / Invisible (Unlisted). Warranties must not be browsable: shoppers add them through the SureBright offer, not from your catalog pages.
Your connectorNon-stock items in sync scope; SKU mappingIncluded; Inventory ID maps to the Shopify SKU.

After the first sync, open one warranty product in Shopify and compare its SKU to the Inventory ID character by character. A product published as SBW-1U-CEA instead of SBW-1U-CEAD-04999 will never reconcile, and fixing it later means unpicking records on both platforms.

Troubleshooting#

SymptomCause and fix
Import reports success but far fewer items than rows; codes cut shortINVENTORY key still 10 characters. Raise to 20, sign out and in, remove the affected items, re-import.
12 items have not been processed successfully. View name: Item.No <Action: Save> row. Add it as the last row, Once for Last Detail.
Can't write CLR type System.String with handler type NumericHandlerBasePrice still typed String on the data provider. Set Decimal and save.
'Tax Category' cannot be emptyNo tax category exists. Create one at TX205500.
The required configuration data is not entered on the Branch formFinish CS101500 and CS102000 before opening Tax Categories.
File '<EmptyFileName>' is not foundThe provider was not saved before upload. Save, then upload through FILES.
Provider Object empty and outlined redSource object not Active on the SCHEMA tab.
Descriptions show mangled charactersEncoding left at US-ASCII. Set UTF-8 and re-prepare.
Items import but carry no accounting treatmentItemClass in the CSV does not match the class ID exactly.
Item will not save, Description requiredExport to External Application makes Description mandatory; every row needs one.

If an issue persists, send SureBright the screen ID, the exact error text and the record count from IN202000.