How to Apply CRV Rules by Customer, Location, and Warehouse in Acumatica

California Redemption Value (CRV) processing in this Acumatica customization uses a customer default-location checkbox to decide whether a linked CRV fee item appears on a sales order. When Include in CRV is selected and a beverage item has a CRV item assigned, adding the beverage line creates a separate fee line. The fee line receives the same quantity and warehouse as its parent beverage line.

The supplied CRV guide documents that customer-location switch and warehouse copy. It does not define a wider rule matrix by ship-to address, store, trading partner, or warehouse. Keep those requests separate from the documented behavior until an implementation test or product specification confirms them.

The Customer Location Is the Eligibility Check

The Include in CRV checkbox is added to the Customer Default Location. Its selected state determines whether the CRV item is displayed on the sales order. The Biz-Tech Services CRV product for Acumatica therefore needs the customer location reviewed alongside the beverage item setup, even when the product's CRV Item field is already populated.

The source calls out the default location. It does not explain how another ship-to or non-default customer location is selected, whether a location change recalculates an existing fee line, or how a customer with several locations should be configured. Earlier published articles discuss broader per-location scenarios, but the supplied product guide does not prove those rules. Test them in the installed customization before using them as policy.

CRV Customer and Warehouse Checks at a Glance

For an order-entry test, check the documented settings in this order:

Open the intended customer's default location and inspect Include in CRV.

Open the beverage Stock Item. On Price/Cost, confirm CRV Item points to the intended non-stock fee item.

Check CRV Amount for the selected unit of measure on the Stock Item. The guide separately locates that field on the General tab.

CRV Stock Item

Add the beverage item to a test sales order for that customer. Confirm one associated CRV child line appears when the checkbox is selected.

Compare the child quantity and warehouse with the parent beverage line.

Review Parent Item and Child Item on the Sales Order, Shipment, and Invoice screens to keep the relationship visible downstream.

This is a validation sequence based on the fields the guide names. The guide does not provide an automated duplicate-fee checker or an order-entry error message for a missing location setting.

How the Warehouse Reaches the CRV Line

The warehouse value comes from the beverage line. When Acumatica adds the associated CRV non-stock item, it sets the same warehouse on that child line. There is no separate CRV warehouse eligibility table or warehouse-to-fee mapping in the supplied documentation.

This matters when an order has lines fulfilled from different warehouses: review each parent-child pair on the sales order instead of assuming a customer-level warehouse default controls all CRV lines. The guide confirms the value copied at line creation, but it does not describe what happens if someone later changes a parent warehouse. Recheck the child before the order proceeds.

Prevent a Missing or Duplicate Fee

The product guide describes one automatic action: adding a qualifying parent beverage item for a customer location with Include in CRV selected creates its associated CRV child line. It does not describe manual fee insertion, duplicate detection, or what happens if the same product is added twice. A useful control is to review each beverage line with its Parent Item and Child Item values and count the fee lines before shipment and invoice creation.

If the CRV line is absent, check the location checkbox first. Then check the beverage item's CRV Item field and confirm that its selected fee item is non-stock. If a fee line appears unexpectedly, confirm the customer default location and the linked beverage item; do not assume the warehouse alone triggered it. For a disputed amount, compare CRV Amount with the selected unit of measure. The manual does not give a conversion or rounding formula.

Keep the Order Accurate Downstream

Parent Item and Child Item fields are available on Sales Orders, Shipments, and Invoices. Use them to see which fee belongs to which beverage line as the document moves through fulfillment and billing. Compare the related lines rather than reconciling a single total that could hide a missing or doubled fee.

The source does not provide a rule for customer account aliases, trading-partner IDs, store codes, or ship-to matching. If those dimensions determine CRV eligibility in your business, document the desired behavior and test it separately. The current CRV guide supports a default-location checkbox, an item-to-fee link, an amount by unit of measure, and warehouse inheritance.

CRV Location and Warehouse: Frequently Asked Questions

Does CRV use the customer account or the location?

The documented switch is Include in CRV on the Customer Default Location. The guide does not describe a separate account-level CRV field.

Can I set different CRV rules for every ship-to location?

The guide names the customer default location but does not explain selection or override behavior for other ship-to locations. Confirm that requirement in the installed customization before promising it.

Does the warehouse decide whether CRV applies?

No warehouse-based eligibility rule is documented. The generated CRV line receives the same warehouse as its beverage parent line.

Why is a CRV line missing from an order?

Check Include in CRV on the customer default location, then the beverage Stock Item's CRV Item link. The selected CRV item should be non-stock.

How can I spot two CRV lines for one beverage line?

Review the sales order's Parent Item and Child Item fields and count the child lines associated with each beverage line. The source does not claim a built-in duplicate-fee alert.

What if the fee line has the wrong warehouse?

Compare it with the parent beverage line. The guide says the child initially receives the parent's warehouse; it does not describe later edit behavior, so retest changes before release.

Use the Documented Scope for CRV Decisions

The customer default-location checkbox controls whether an associated fee line appears. The beverage Stock Item chooses the CRV non-stock item and its amount, while the sales order copies the parent line's quantity and warehouse to the child. Review that pair again on the shipment and invoice. Additional location, store, or trading-partner rules need their own approved specification.

For help validating customer-location CRV behavior in your Acumatica setup, contact Biz-Tech Services at https://biz-techservices.com.


How to Track Gift Card Customers and Recipients in Acumatica

Gift Card Processing in Acumatica stores a Customer ID with each sold gift card, along with the Order Number, Inventory ID, serial number, and amount details. The product guide does not document a separate recipient field or a rule that maps a card to a ship-to contact, store, location, or trading partner. If a gift is purchased for someone else, the documented Customer ID should be treated as the customer on the sale, not proof of who received the card.

The useful link is the card's serial number. From the Gift Cards tab on Payment Methods, a user can open Gift Card History for that serial and review related activity. The guide also describes customer information arriving with gift cards created through the Biztech endpoint, although it does not specify the API's customer-field mapping.

What Customer Information Follows a Gift Card Sale

A gift card can be sold as a non-stock item or as a serialized stock item on a standard Acumatica sales order. After the sale, the Gift Cards tab on Payment Methods lists Customer ID, Inventory ID, Gift Card Serial Number, Order Number, Gift Card Amount, Used Amount, and Remaining Amount. For a stock card, the sales order uses a selected lot or serial number; for a non-stock card, the number may be entered or generated according to Gift Card Preferences (BZ102000).

Gift Card Preferences

Those fields let staff trace a card back to the order and customer record captured by the sale. The guide does not define a recipient account, recipient email, or card-owner field. It also does not say that later redemption changes the original Customer ID. Keep purchase, delivery, and redemption identities separate in any business procedure until your implementation documents how each is recorded.

Gift Card Customer Tracking at a Glance

At sale, confirm the sales order is on the intended customer before the gift card is fulfilled.

Record or generate the card number. For a stock gift card, select the allocated serial number on the sales order line.

After sale, compare Customer ID and Order Number with the Gift Card Serial Number on the Payment Methods Gift Cards tab.

Open Gift Card History (BZ407099) from the serial number to review activity for that card.

If a card is created through the external API, verify the customer information displayed on Payment Methods, Gift Card Summary, and Gift Card History.

This is a review sequence for people using the documented screens. The manual does not describe a built-in duplicate-customer check or an automated recipient match.

Keep the Purchaser and Recipient Distinct

A buyer may purchase a card as a gift. In the documented workflow, the sales order has a customer and the resulting gift card record has a Customer ID. The guide never states that this ID changes to the person who receives the card. It gives no field where a recipient name, address, or email is captured for a gift card.

For downstream order accuracy, check the sale's customer and order number against the card record before answering account questions. Use the serial number when asking about a specific card's balance or history. If your business needs a separate recipient record or delivery instruction, define where that information will live and how staff will verify it. The Gift Card Processing guide cannot supply that mapping.

Check Customer Information on External Gift Cards

The guide says the Create Gift Card action in the Gift Card History endpoint can import gift card information from an external system through the Biztech API. After the request is processed, customer information, serial number, and amount appear on the Gift Cards tab of Payment Methods and on Gift Card Summary and Gift Card History.

Gift Card History

The guide does not list the API request fields or explain how an external customer identifier is matched to an Acumatica Customer ID. It also gives no duplicate rule for two API requests with the same customer or serial number. For a new integration, test a small set of cards and compare the resulting Customer ID and serial number with the external source before increasing volume.

Avoid Duplicate and Misassigned Card Records

Gift Card Preferences controls how non-stock gift card numbers are generated. It offers numbering segments or random numbering. Stock cards use serial numbers generated during receipt and selected during allocation. These are number-generation methods, not documented customer-deduplication rules.

Use a concrete review: look up the card's serial number, check the linked Order Number and Customer ID, and inspect Gift Card History before creating a second card for the same request. If a customer account was entered incorrectly on the source order or an external API request, the guide does not describe a reassignment or merge action for the card. Resolve the record with the implementation team rather than assuming an account edit will move the gift card history.

Where to Check Customer and Card Details

Sales Orders: review the customer and gift card line on the sale that created the card.

Payment Methods Gift Cards tab: compare Customer ID, Inventory ID, Gift Card Serial Number, Order Number, Gift Card Amount, Used Amount, and Remaining Amount.

Gift Card History: open the card by serial number to review related transactions.

Gift Card Summary: inspect the card details displayed after an external API creation.

The guide names no recipient, ship-to, store, location, or trading-partner field in those gift card views. Check such information in the original business process if your team records it elsewhere; do not present it as a built-in Gift Card Processing mapping.

Gift Card Customers and Recipients: Frequently Asked Questions

Does Customer ID identify the gift card recipient?

The guide does not say that. It stores Customer ID with the sold card and its Order Number, but defines no separate recipient field.

Can a gift card be linked to a ship-to address or store?

No such link is documented for the gift card record. A delivery or store requirement needs its own confirmed workflow.

How do I trace a card back to the original sale?

Use the Gift Card Serial Number and Order Number on the Payment Methods Gift Cards tab, then open Gift Card History for the serial.

Where does the customer appear for an API-created gift card?

The guide says customer information appears on Payment Methods, Gift Card Summary, and Gift Card History after the Create Gift Card API action is processed.

Does Gift Card Processing prevent duplicate customer accounts?

The documentation does not describe a customer-deduplication feature. Verify the customer record used by the source order or external request before creating cards at scale.

Can the customer on a sold gift card be changed later?

The guide gives no reassignment procedure. Confirm the correction path with your implementation team before changing a source order or customer record.

To review your gift card customer and recipient workflow, contact Biz-Tech Services at https://biz-techservices.com.


How to Manage Consignment Customers and Locations in Acumatica

In Acumatica, Biz-Tech Services Consignment Processing uses the customer selected on a Consignment Order to identify which consignee holds the stock. A Consignment Warehouse assigned to that customer overrides the default warehouse in Sales Order Preferences. Check both values before confirming a shipment: the customer identifies the consignee, while the warehouse identifies where the consigned inventory will be tracked.

The product guide documents this relationship and the order, sale, return, and physical-count steps that follow it. It does not describe an external trading-partner map, a customer deduplication tool, or automatic matching of multiple ship-to locations under one customer. Those requirements need their own design and testing.

Customer and Consignment Warehouse at a Glance

This is the documented Acumatica path from consignee selection to stock at the customer location:

Mark an eligible destination warehouse Use for Consignment on Warehouses (IN204000).

Set a default Consignment Warehouse in Sales Order Preferences (SO101000), if the implementation uses one.

On the customer record, set the Consignment Warehouse for that consignee. The manual shows this field on the Shipping tab.

Create a Consignment Order on Sales Orders (SO301000), choose Order Type CN, and select the intended Customer.

Confirm the resulting destination warehouse. The customer's assignment takes priority over the preferences default.

After Shipment Confirmation and Update IN, review the order and warehouse before selling, returning, or counting the stock.

This sequence is a customer-to-warehouse relationship. It does not create a separate recipient record for each shipment or translate an external partner ID.

Set the Warehouse on the Correct Customer

The Customers section of the guide says the selected customer's specific Consignment Warehouse is used for the sales order. Its screenshot shows the Consignment Warehouse field under the customer's Shipping tab. This assignment overrides the default Consignment Warehouse in Sales Order Preferences.

A default can help populate orders, but it cannot tell you which of two similar Acumatica customer records is the right consignee. Before creating an order, confirm the customer name and the warehouse assigned to that record. If a business keeps separate customer records for separate consignee sites, maintain a clear owner for those records and review the warehouse on each one. That is a data-quality practice, not an automated duplicate rule claimed by the product guide.

The guide does not specify a customer form ID, a location-specific override under a single customer, or how two ship-to addresses sharing one customer should choose different consignment warehouses. Test that design in the configured Acumatica system before promising site-level separation.

Create the Order for the Intended Consignee

On Acumatica Sales Orders (SO301000), select CN as the Order Type and choose the corresponding Customer. Add the items and quantities being sent. The consignment order is associated with that customer, so a wrong customer selection would put the transaction under the wrong consignee in the documented process.

Review the destination warehouse before Shipment Confirmation. The guide allows a consignment warehouse only as the destination and a standard, non-consignment warehouse only on the lines. Reversing those roles produces an error notification, though the guide does not provide the message text.

After Shipment Confirmation, use Update IN. The guide says this issues the items from the main warehouse and receives them into the selected consignment warehouse, creating and releasing a Transfer-type Purchase Receipt. Check the resulting Acumatica order and receipt before the consignee reports sales or returns.

Keep Sales and Returns with the Original Order

When the order reaches Consignment or Partial Consignment, the Consignment Sell Items and Consignment Return Items actions become available. Both start from the Consignment Order's Item Selection pop-up. A sale produces a Consignment Invoice Order; a return produces a Consignment Return Order.

Starting from the correct original order keeps the documented customer, warehouse, item, and quantity context together. The guide does not describe moving an open consignment balance from one customer to another or merging duplicate Acumatica consignee records after shipment. Resolve a mistaken identity with an approved business process instead of assuming those actions exist.

Order-level records remain in the Consignment Orders Generic Inquiry. The Consignment Item Details inquiry shows open item-level information, but the guide says closed orders no longer appear there at item level. Use the order-level inquiry when checking a completed history.

Use Physical Counts to Check Customer and Location

The manual also ties Acumatica physical counts to a customer and location. On Physical Inventory Types (IN208900), selecting Consignment Inventory Count exposes Customer and Location fields for the physical-inventory type. Consignment orders must already exist for the relevant customer and warehouse.

Prepare Physical Count (IN504000) then shows Inventory IDs and Book Qty for the chosen count type. The guide defines Book Qty as the sum of Open Qty from related consignment orders for the specified customer and warehouse. Generate PI opens Physical Inventory Review (IN305000), where staff enter Physical Qty, finish counting, and complete the count.

Prepare Physical Count Generate PI

The count can generate a Consignment Invoice Order for the recorded difference. Before completing it, compare the customer, location, warehouse, and open order balances. An Acumatica physical count is a useful reconciliation point, but it does not replace choosing the correct consignee on the original order.

Where to Check Your Work

Customers > Shipping: confirm the Consignment Warehouse on the selected consignee record.

Sales Order Preferences (SO101000): note the default Consignment Warehouse and the configured order types.

Warehouses (IN204000): confirm Use for Consignment on the destination warehouse.

Consignment Warehouse

Sales Orders (SO301000): verify Order Type CN, Customer, destination warehouse, source warehouse on lines, items, and quantities.

After Update IN: verify the Consignment or Partial Consignment status and the transfer receipt.

Consignment Orders and Consignment Item Details inquiries: review open order and item balances; use order-level history for Closed orders.

Physical Inventory Types (IN208900) and Prepare Physical Count (IN504000): verify the Customer, Location, related Inventory IDs, and Book Qty before counting.

Consignee Customer and Location: Frequently Asked Questions

Which warehouse wins when the customer has one assigned?

The customer's Consignment Warehouse overrides the default in Sales Order Preferences for the selected order.

Where is the customer's Consignment Warehouse shown?

The guide's customer screenshot shows the field on the Shipping tab. It does not name a customer form ID.

Can one customer use different warehouses for different ship-to locations?

The supplied guide does not describe that selection rule. Confirm the configuration and test each location before using it as an operating assumption.

Does Consignment Processing prevent duplicate customer records?

No duplicate-customer rule is documented. Review the consignee record and its warehouse assignment before creating the order.

Why is the warehouse rejected on a consignment order?

Check its role. The consignment warehouse belongs in the destination; a standard non-consignment warehouse belongs on the lines. The guide says the wrong choice raises a notification but gives no exact error text.

Where can I check a closed consignee order?

Use the Consignment Orders Generic Inquiry for order-level information. The Item Details inquiry stops showing item-level information for Closed orders.

Keep the Consignee Record Traceable

A reliable Acumatica consignment process starts with the right customer and assigned Consignment Warehouse, then checks the same relationship on the order and physical count. Make customer and warehouse ownership explicit in your team procedures when several consignee sites have similar names.

For help validating consignee and warehouse setup in Biz-Tech Services Consignment Processing, contact the team at https://biz-techservices.com.


How to Assign Kit Sales to the Right Customer and Ship-To in Acumatica

A kit sale needs the correct customer and ship-to on its Acumatica sales order before the kit is fulfilled. The Biz-Tech Services Kit Processing guide explains how a kit line expands into a placeholder and components, then moves through shipment and invoicing. It does not define a customer-matching rule, a ship-to mapping table, or a duplicate-customer check. Review the order's customer and destination through the normal order-entry process, then check the kit-specific settings that can change what happens to that order.

This distinction is especially useful when an imported order appears under the wrong account or address. Kit Processing handles kit specifications, options, component lines, pricing, and fulfillment.

What Kit Processing Can Check on a Customer Order

On a sales order, users add a kit item and can review its Component Details. The kit specification can require option choices, allow substitutions, and decide whether the kit explodes. When it does explode, the order shows a non-stock placeholder item and the component lines. The guide then takes that order through Create Shipment, Confirm Shipment, Prepare Invoice, and Release.

One documented customer-level control matters here: Block Kit Items Explosion on the Customers or Vendors screen can stop a kit from exploding. The same control on Order Types can also stop it. This setting changes the kit line behavior for an order; it is not a customer assignment or ship-to mapping rule. If two otherwise similar orders show different kit lines, compare the customer record and order type before changing the kit specification.

Sales Order Preferences Quantity Availability

Customer and Ship-To Review at a Glance

Use this as an order-review checklist. The customer and destination checks are business validation steps; the supplied Kit Processing guide does not describe an automated matching feature.

Identify the intended customer and delivery destination from the original request or external order.

Open the Acumatica sales order and confirm that its customer and ship-to match that source before processing the kit line.

Check whether Block Kit Items Explosion is enabled for the customer or order type. A blocked kit can remain unexploded even when its specification allows explosion.

Review the kit item's selected options and Component Details before explosion. Confirm the expected placeholder and component lines afterward.

After Create Shipment and Confirm Shipment, compare the shipment with the approved order before Prepare Invoice and Release.

Do not treat a matching kit inventory ID as proof that the customer or address is right. Those are separate parts of the order. The manual does not specify the exact customer and ship-to field labels or an address validation message for this workflow.

Prevent Duplicate Customer Assignments Upstream

The manual provides no rule for merging duplicate customer accounts or identifying that two external names refer to one Acumatica customer. For imported orders, agree on a stable account identifier and review ambiguous matches before the order enters fulfillment. That is an implementation recommendation, not a Kit Processing feature documented in the guide.

Keep a short exception list during testing: one existing customer with more than one ship-to, two similar customer names, a missing external account identifier, and a repeated order. Record the expected customer and destination for each sample. If the result differs, review the import or connector mapping that created the sales order. The kit specification will not tell you which customer account an external buyer should become.

Check Kit Behavior After the Customer Is Correct

Correct customer assignment does not by itself guarantee the expected kit lines. The Kit Specifications screen has an Active flag and Current Revision; the manual says the current revision is needed for explosion on a sales order. Explode Option can Prompt, Automatically explode, or Do Not Explode. The customer and order-type block settings can prevent explosion regardless of that option.

Review the Options popup and resulting component lines before fulfillment. Required option codes need a selection; automated order paths can use a configured Default Code. These controls affect kit contents on the order, not customer or ship-to assignment.

Follow the Approved Order Through Fulfillment

After kit explosion, the guide's fulfillment sequence is Create Shipment, Confirm Shipment, Prepare Invoice, and Release. Recheck the destination against the approved sales order at the shipment stage. The manual does not say that Kit Processing copies, changes, or validates a ship-to address at any of these steps, so a deployment-specific test is needed before making that claim.

Component availability can still affect timing. Sales Orders Preferences offers shipping choices based on available and ordered component quantities. A delayed shipment after customer and destination checks may be an availability issue rather than a mapping issue; the prior kit-fulfillment article covers those settings in detail.

Where to Check Your Work

Source request or external order: keep the intended customer, destination, and order reference available for comparison.

Sales Orders: confirm the account and ship-to chosen for the order, then inspect the kit line and Component Details.

Customers or Vendors: inspect Block Kit Items Explosion if the kit remains unexploded for a particular account.

Order Types: inspect the same blocking control when several orders of one type behave alike.

Kit Specifications: confirm Active, Current Revision, Explode Kit, and Explode Option for the selected kit.

Shipments and Invoices: compare the created documents with the approved order before confirming and releasing them.

The guide names these kit and fulfillment areas but provides no customer-alias table, ship-to cross-reference inquiry, or duplicate-account queue. Document those controls separately if your order source needs them.

Kit Customer and Ship-To: Frequently Asked Questions

Does Kit Processing choose the sales order customer?

The guide does not describe that capability. It starts its kit workflow after a kit item is added to a sales order.

Does the product map an external address to an Acumatica ship-to?

No ship-to mapping rule is documented. Test the connector or import scenario that creates the order and compare its result with the source order.

Why does a kit explode for one customer but not another?

Check Block Kit Items Explosion on the customer record, then check Order Types and the kit specification. The manual identifies both blocking settings as overrides of the selected explode option.

Can an imported kit order be linked to a duplicate customer?

The Kit Processing manual does not provide duplicate prevention. Use a controlled account identifier in the import or connector mapping and review ambiguous matches before fulfillment.

What should I check before confirming shipment?

Compare the shipment destination with the approved order, then review placeholder and component lines and the selected component-quantity shipping rule. The destination check is an order control; the component checks are documented Kit Processing behavior.

Will a customer correction update an already-created shipment?

The manual does not describe that behavior. Verify the result in your Acumatica deployment before changing an order with downstream documents.

Keep Customer Mapping Separate From Kit Configuration

A reliable kit sale starts with a verified sales order customer and destination, followed by a check of the kit's options, explosion controls, and fulfillment documents. The supplied guide supports the latter workflow. It leaves account matching, ship-to translation, and duplicate detection to be specified and tested for the order source.

If your team needs to review kit order behavior alongside customer and ship-to requirements, discuss your Acumatica workflow with Biz-Tech Services at https://biz-techservices.com.


How to Map ServiceTitan Pricebook Items to Acumatica Inventory Items

ServiceTitan pricebook items can be brought into Acumatica as new items or mapped manually to existing items. The Biz-Tech Services ServiceTitan Acumatica Connector documents both paths. Its Inventory area can load Materials, Equipment, and Services for review; its item-generation option uses the selected stock item class, non-stock item class, and unit of measure. The current product page also describes a Pricebook view that shows the ServiceTitan item code, name, unit of measure, price, and item type.

Those facts establish a review workflow, but not an automatic code-matching formula. Neither the supplied workflow document nor the product page names an alias table, a duplicate-code rule, or the exact field used to pair a ServiceTitan code with an Acumatica Inventory ID.

Start With the ServiceTitan Store Inventory Settings

The ServiceTitan Store governs item handling alongside invoice imports, warehouse mapping, and inventory transactions. Configure and test the store connection before loading item data. The Biz-Tech Services Acumatica ServiceTitan Connector provides Test Credentials for the connection settings; a successful test confirms access to the ServiceTitan store, not the correctness of an item map.

In the Inventory area, selecting Import Item makes Generate Item from ServiceTitan available. The manual also says ServiceTitan items can be mapped manually to Acumatica items instead of being created. Use Load Materials, Equipment, Services to display the source items on the Inventory tab, then review what each row should become before importing transactions against it.

The product page adds a dedicated Pricebook view with item code, name, unit of measure, price, and item type. It does not publish a screen ID or describe which of these values acts as the match key. Treat the code as an identifier to inspect and reconcile, not as a confirmed automatic Inventory ID mapping rule.

Pricebook Item Mapping at a Glance

The Biz-Tech Services ServiceTitan Acumatica Integration supports this practical sequence:

Test the ServiceTitan Store connection and confirm that the intended store is selected.

Load Materials, Equipment, and Services and compare the loaded rows with the Pricebook view's code, name, unit of measure, price, and type.

For each source item, choose an existing Acumatica item for manual mapping or approve creation of a new one.

For generated items, review Stock Item Class, Non-Stock Item Class, and Unit of Measure before using Generate Item from ServiceTitan.

Test a small invoice or inventory transaction and inspect the Acumatica item and related warehouse before widening the import scope.

The first four controls are documented. The last step is a validation recommendation: the source describes invoice and inventory imports but provides no formal item-map test procedure.

Choose an Existing Inventory Item or Generate a New One

Manual mapping is the documented path when the Acumatica item already exists. Review its Inventory ID and business meaning against the loaded ServiceTitan row. A matching name alone is a weak basis for approval; the available Pricebook code, type, unit of measure, and price give reviewers more context, though the sources do not say which values the connector itself compares.

For a new Acumatica item, the manual says Materials and Equipment generate stock items, while Service generates non-stock items. Generate Item from ServiceTitan uses the Stock Item Class, Non-Stock Item Class, and Unit of Measure values in the store configuration. Approve those defaults before creation. An incorrect class or unit can make a newly created item unsuitable for the transactions that follow.

Keep a record of the owner who approved each creation or manual link. The sources do not describe a built-in approval queue. This is a project control for avoiding duplicate item masters, not a product feature claimed by the documentation.

Cross-References, Aliases, and Unmapped Records

The Biz-Tech Services Acumatica ServiceTitan Integration documentation confirms manual mapping but does not show an item cross-reference table or an alias field. The current product page says the Pricebook view preserves cross-system identifiers, yet it does not explain how multiple codes, renamed items, or duplicate codes are resolved.

List ambiguous rows before enabling broad item creation or transaction imports. For each one, record the ServiceTitan code and name, the intended Acumatica Inventory ID, the unit and type, and the person who decided the link. If a code has no safe match, leave the disposition open until a controlled test establishes what the connector does. No item-specific error text or unmapped-item queue is provided in the source.

Warehouse and truck IDs are a separate map on the ServiceTitan Store. Load Warehouses retrieves those values so they can be paired with Acumatica warehouses. A correct item link does not substitute for that location mapping when receipts, transfers, adjustments, or returns are imported.

Validate the Link With a Small Import

A loaded row is only the beginning of validation. Choose a small set that includes a Material, Equipment item, and Service line, plus one item that was mapped manually. Inspect the generated or linked Acumatica records, including item type, class, and unit of measure. Then process a representative transaction and confirm it uses the intended item.

For invoice imports, the Import SO Invoices screen retrieves ServiceTitan invoices by updated date and selected status, and creates them in Acumatica's Invoices and Memos screen. For inventory movements, the manual lists receipts, transfers, adjustments, and returns, each with its own release-after-import choice. If a transaction looks wrong, first separate item choice from warehouse and release settings; these controls live in different parts of the store setup.

The supplied guide does not provide a field-by-field pricebook-to-invoice-line map or an item-specific validation message. Save a test result that shows the source code, chosen Inventory ID, resulting document line, and any observed exception. That gives the team evidence for a mapping decision without implying an undocumented rule.

Where to Check Your Work

The Biz-Tech Services ServiceTitan Acumatica Integrator exposes the documented controls in these locations:

ServiceTitan Store and Connection Settings: confirm store selection and Test Credentials result.

Inventory area: review Import Item, Generate Item from ServiceTitan, Stock Item Class, Non-Stock Item Class, and Unit of Measure.

Inventory tab: inspect the rows retrieved by Load Materials, Equipment, Services and the manually chosen item relationships.

Pricebook view: compare the published item code, name, unit of measure, price, and item type with the approved item decision.

Warehouses mapping: check ServiceTitan Warehouse and Truck IDs against Acumatica warehouses before testing inventory movements.

Import SO Invoices and Invoices and Memos: review a sample imported invoice and its item lines.

Inventory Transactions tab: check receipt, transfer, adjustment, and return settings, including release-after-import choices.

ServiceTitan Pricebook Mapping: Frequently Asked Questions

Does the connector require new Acumatica items for every ServiceTitan item?

No. The workflow document says users can manually map ServiceTitan items to existing Acumatica items instead of generating new records.

Which ServiceTitan types generate stock items?

Materials and Equipment generate stock items; Service generates non-stock items. The selected item classes and unit of measure are inputs to generation.

Is the ServiceTitan item code automatically the Acumatica Inventory ID?

The product page says the Pricebook view shows ServiceTitan item code, but neither source specifies that the code becomes Inventory ID or defines the match formula. Verify the relationship in the installed connector.

Can one ServiceTitan item use multiple aliases?

The supplied sources do not document an alias field or multiple-code precedence. Record the requirement and test it before relying on it.

Where is an unmapped-item error shown?

No item-specific error message or exception queue is named. Review the loaded inventory rows and resulting test document; capture any actual message from your configuration.

Why might a mapped item still fail in an inventory transaction?

Check the separate ServiceTitan Warehouse or Truck ID mapping and the transaction settings. The documentation requires the related purchase order before a purchase receipt or bill can be imported.

ServiceTitan Purchase Orders

Approve the Map Before Scaling Imports

The documented choice is straightforward: link each loaded ServiceTitan item to an existing Acumatica item or generate a new stock or non-stock record using reviewed class and unit settings. The Pricebook view helps reviewers compare catalog identifiers and attributes. Duplicate-code, alias, and unmatched-item behavior still need an agreed test result because the sources leave them unspecified.

For help reviewing ServiceTitan item mappings and testing sample imports, contact the Biz-Tech Services Acumatica ServiceTitan Integrator team at https://biz-techservices.com.

Sources: Biz-Tech Services, Service Titan - Acumatica Integration workflow document, Inventory and Import SO Invoices sections; and ServiceTitan Integration product page, https://biz-techservices.com/servicetitan-integration (accessed October 26, 2026).


How to Map Salesforce Products to Acumatica Items

To map Salesforce products to Acumatica items, match Salesforce Product SKU to the Acumatica Inventory CD. The integration guide says the import looks up Inventory CD using Product SKU. A match retrieves the existing item. If there is no match, the Import Item setting determines whether the integration may create a new item or stops with a missing-item error.

That is the documented identity rule for the Biz-Tech Services Salesforce Acumatica Connector. Item Details also shows Salesforce ID, product code, product name, price, and weight after synchronization, but the guide does not make any of those values an alternate key for the SKU lookup.

Check the Salesforce Store Item Settings

The Biz-Tech Services Acumatica Salesforce Connector places product controls in Salesforce Store under Item Settings. Review the settings before you import an order or synchronize the catalog:

Import Item allows new ERP items to be created from Salesforce products when selected. When cleared, the item must already exist in the ERP.

Add Items in Inventory Sync enables synchronization with Salesforce items.

Use Numbering Sequence for Product ID Generation generates a unique product ID for a new product from a predefined numbering sequence.

The guide does not identify item class, stock status, unit of measure, or a default warehouse as item-creation rules in this section. Set those requirements separately with the implementation team instead of assuming the checkbox supplies them.

Salesforce Product Mapping, Step by Step

The practical sequence is short. Use a small, known set of products to test the decisions before opening the full catalog.

Identify each Salesforce Product SKU and the Acumatica Inventory CD it should resolve to. Correct mismatches in the source records or target item setup before import.

Decide whether Import Item may create missing items. Leave it cleared when every imported product must match an existing Inventory CD.

In Salesforce Store, use Item Details and Load Acumatica items to display existing ERP items for review.

Use Sync all from Salesforce when the approved task is to retrieve and create Salesforce items in Acumatica. Use Sync to Salesforce when approved Acumatica items should be created or updated in Salesforce.

After a test, review Salesforce ID, product code, product name, price, and weight in Item Details. Confirm that the intended item was used or created.

For order retrieval and import steps, see the related lesson, How to Import Salesforce Orders into Acumatica.

What Happens to an Unmatched SKU?

The Biz-Tech Services Salesforce Acumatica Integration guide gives one explicit item-mapping exception. With Import Item cleared, a Salesforce Product SKU that does not find an Inventory CD produces the message 'The item {0} does not exist in the system.' The source prints the placeholder {0}; it does not show a completed example with a product value.

With Import Item selected, the guide says new ERP items are created based on configured settings. It does not name every required field or explain whether a duplicate Salesforce product can produce a duplicate item. Test creation with one product and review the resulting record before using the option at scale.

The guide does not describe an unmapped-product queue or a retry workflow. For a failed import, start by comparing Product SKU with Inventory CD and confirming the Import Item choice. Record any additional behavior seen in your own environment before making it an operating rule.

Cross-References, Aliases, and Item Classes

The Biz-Tech Services Acumatica Salesforce Integration has Cross-Reference Options and a Cross-Reference tab, but the guide's examples are Payment, Country, and Ship Via. It does not identify product aliases or alternate item IDs as Cross-Reference mappings. Product SKU to Inventory CD remains the documented item lookup.

Salesforce Cross-Reference Options

The guide also does not state how the lookup handles letter case, leading zeros, punctuation, or multiple aliases. If two identifiers could be interpreted as the same product, settle the intended SKU and Inventory CD before a live import. That review is an implementation check, not a connector rule described by the manual.

Customer Class appears elsewhere in the Salesforce Store settings for customer creation during order import. It is not an Item Class setting. The source gives no item-class mapping rule.

Price Books Follow the Product Relationship

Price Book Details and Salesforce Price Books handle membership and list price after products are available. The guide says an item must first be included in the standard price book before it is added to another price book. It also says a product already in a Salesforce price book is brought into Acumatica through order import and added to the corresponding price book.

Export Salesforce Price Books processes selected or all price books, while the guide says only changed items are exported. These screens help verify where a product appears and its list price; they do not provide a second documented SKU-matching rule.

Where to Check Your Mapping

The Biz-Tech Services Salesforce Acumatica Integrator provides these checkpoints in the manual:

Salesforce Store > Item Settings: confirm Import Item, Add Items in Inventory Sync, and product ID numbering choices.

Item Details: compare Salesforce ID, product code, product name, price, and weight with the intended item.

Load Acumatica items: display the available ERP items before synchronizing.

Import Salesforce Orders: use Get Orders and then Import or Import All only after testing the SKU match on a small set.

Salesforce Price Books: check standard price book membership and the desired list price where price books are in scope.

The manual supplies no Acumatica screen IDs for Salesforce Store, Item Details, or its price-book screens. Use their displayed names rather than assuming an ID.

Salesforce Product Mapping: Frequently Asked Questions

Which field connects a Salesforce product to an Acumatica item?

Salesforce Product SKU is used to search Acumatica Inventory CD during import.

What if Product SKU does not match an Inventory CD?

With Import Item cleared, the documented error says the item does not exist. With Import Item selected, the integration can create an item according to configured settings.

Does Salesforce ID replace Product SKU as the lookup key?

The guide displays Salesforce ID in Item Details but does not say it replaces the Product SKU lookup.

Can the Cross-Reference tab hold product aliases?

The guide does not document that use. Its Cross-Reference examples are Payment, Country, and Ship Via.

Does Item Class control mapping or item creation?

No item-class rule is specified in the product section. Customer Class is a separate customer-import setting.

Where can I verify a synchronized product?

Open Item Details and review the Salesforce ID, product code, product name, price, and weight. Compare them with the intended ERP item.

Confirm the SKU Rule Before Expanding the Catalog

The safest test is one known match and one intentionally unmatched SKU. Check which item the first resolves to and how the second behaves under the chosen Import Item setting. Keep the result with your implementation record, especially when product IDs or price books are also synchronized.

For help reviewing the Product SKU to Inventory CD rule in your setup, contact the Biz-Tech Services Acumatica Salesforce Integrator team at https://biz-techservices.com.


How to Map Clover Items and SKUs to Acumatica Inventory Items

Clover items are matched to Acumatica inventory items by SKU in the Biz-Tech Services Clover Connector. The product page says a visible cross-reference shows which records are linked and which need review. It also says Clover items can create Acumatica records, while Acumatica items can be published to Clover with a description, price, and category. Those options make a clean SKU list and a deliberate owner for item changes essential before a full catalog is connected.

The published product description confirms the capabilities above, but does not name a mapping screen, exact field labels, duplicate-SKU behavior, or an automatic resolution rule. Treat the checks below as an implementation checklist to test in your own configuration.

What an Item Link Has to Support

The Clover Connector brings register sales into Acumatica as invoices or sales orders. The published description says each resulting document has a line for every item sold, at the price charged at the register. It also carries the sale's discount, service charge, tip, and tax. For the item line to be useful in inventory and reporting, the SKU relationship must point to the intended Acumatica item.

The connector's cross-reference is the place the product page tells operators to distinguish linked items from records needing review. That is a narrower claim than assuming every incoming SKU is safe to import. A visible link should be checked against the product, unit, and selling context before it is accepted for production transactions.

Clover SKU Mapping at a Glance

Use this sequence as a controlled rollout, rather than turning on the full catalog at once:

  • Export or review the current Clover item list and the Acumatica item list. Identify the SKU value each system uses for the same product.
  • Separate one-to-one SKU matches from missing, duplicate, and ambiguous values. Assign an owner to resolve each exception.
  • Review the connector's visible cross-reference. Confirm the intended Clover item points to the intended Acumatica record.
  • Decide whether an unmatched Clover item should create a new Acumatica record or wait for a catalog owner to create and approve one.
  • Run a small sale through the connector's pull and import steps. Check the item line, charged price, discount, tip, tax, and resulting document.
  • Publish or synchronize a small set of approved items, then verify description, price, category, and stock figures at the register before widening the scope.

The product page documents SKU matching, item creation, item publishing, two-step sale import, and quantity export. It does not prescribe this exact rollout order. The sequence is an editorial recommendation for validating those documented functions.

Clean the Catalog Before Matching

Start with records that a person can identify without guessing. For each SKU, note the item name, the intended Acumatica inventory record, and whether the item should be sold at the register. A blank SKU, reused code, or code assigned to different products needs a decision before the cross-reference is approved. The published Clover page does not say how the connector handles those cases.

Keep duplicate handling in the project record: which product keeps the code, which product gets a new code, and who authorizes the change. If multiple Clover records seem to point to one Acumatica item, confirm whether that is intentional in a test transaction. Do not assume the connector merges or rejects them automatically; no such rule appears in the product description.

Catalog cleanup is also where the team chooses a direction for new items. The connector can create Acumatica records from Clover items and publish Acumatica items to Clover. Decide who approves a new record and which system provides its description, price, and category. Otherwise, a mapping review can become an accidental item-master change.

Review the Cross-Reference and Unmatched Items

The visible cross-reference is useful because it exposes links that exist and links still needing review. Check it before importing a batch of register sales or publishing more products. For each sampled record, compare the Clover SKU with the intended Acumatica inventory item, then verify the item used on an imported document line.

The product page does not give a named unmatched-item queue, a screen ID, or a specific error message for an unknown SKU. It does say sales are pulled and imported in two deliberate steps, which gives an operator a chance to review before posting and retry a sale that needs attention. Record what an unmatched item does in a test sale, including any message and whether the document remains unposted. That result is more useful than guessing from a generic integration pattern.

Set Ownership for Item, Price, and Stock Changes

Item mapping is a business decision as well as a connector setting. The official description supports two item directions: Clover items can create Acumatica records, and Acumatica items can publish to Clover with description, price, and category. Choose an approval path for each direction and document who changes an existing item when the two catalogs disagree.

Stock has a more explicit owner. The product page calls Acumatica the source of truth for quantities. A business can choose on-hand, available, or available-for-shipping quantity and can draw it from one warehouse or the whole company. Confirm that choice before publishing quantities to Clover. The connector shows the quantity Clover holds and when it was last sent, which gives the team a check after the export.

Test a Small Transaction Set Before Expanding

A mapping that looks right in a list still needs a transaction test. Include a normal sale, a sale with multiple items, and a known exception. The documented import creates an Acumatica invoice or sales order with an item line for each Clover item sold. Compare those lines with the Clover receipt, including the price charged, discount, service charge, tip, and tax. The page says sales can be reviewed between pull and import, and retried when attention is needed.

Returns deserve a separate check. The connector description says a register refund becomes an Acumatica credit memo against the original invoice and carries returned lines, discounts, and tax. Verify that the returned item is the same item that appeared on the sale. Then check one approved item published from Acumatica to Clover and one inventory quantity export. Only after these examples reconcile should the team expand the connected catalog.

Where to Check Your Work

  • Compare the visible Clover-to-Acumatica cross-reference with the approved SKU list; note links that still need review.
  • During the two-step sale import, inspect a sampled sale before posting and retry any sale that needs attention.
  • On the resulting invoice or sales order, compare each imported item line and charged price with the register receipt.
  • For a return, compare the credit memo's returned lines with the original invoice and refund.
  • After an item publish, check its description, price, and category in Clover.
  • After quantity export, check the quantity Clover holds and the recorded last-sent time against the chosen Acumatica quantity basis.

Export Item Quantities to Clover mapping screen

Clover Item Mapping: Frequently Asked Questions

What does the Clover Connector use to match products?

The Biz-Tech Services product page says products are matched on SKU and that a visible cross-reference shows linked items and items needing review. It does not specify additional identifier precedence.

Can an unmatched Clover item create an Acumatica record?

The page says Clover items can create Acumatica records. It does not publish the exact conditions, defaults, or approval controls. Test the behavior and assign an item owner before enabling it for a broad catalog.

What happens when two Clover products share a SKU?

The published description gives no duplicate-SKU rule. Resolve the duplicate in the source catalog or verify the configured behavior with a controlled test before importing those products.

Does the connector show items that still need review?

Yes. The product page says the visible cross-reference shows what is linked and what still needs review. It does not give the screen name or a separate unmatched-item queue.

Which system owns the stock quantity shown in Clover?

The page identifies Acumatica as the quantity source. The business chooses the quantity basis and whether to use one warehouse or the whole company.

How can I tell whether a test sale used the right item?

Compare the Clover receipt with the imported Acumatica invoice or sales order. Check each item line and price, then review any discount, service charge, tip, and tax recorded on the document.

Keep the SKU Link Reviewable

A workable Clover item map has an approved SKU list, a reviewed cross-reference, an owner for new and changed records, and test transactions that match the register receipts. The connector's documented two-step import and visible links give the team places to check its work. Screen names and duplicate-handling rules still need confirmation in the installed configuration.

For a review of Clover catalog mapping and transaction tests in Acumatica, contact Biz-Tech Services at https://biz-techservices.com.

Source: Biz-Tech Services, Clover Connector product page, https://biz-techservices.com/clover-connector (accessed October 26, 2026).


How to Map Salesforce Products to Acumatica Items

Mapping Salesforce products to Acumatica items begins with Salesforce Product SKU and Acumatica Inventory CD. During import, the connector searches Inventory CD using Product SKU, retrieves the matching item when one exists, and either creates a new item or displays an error when no match exists, depending on the Import Item setting.

The Biz-Tech Services Salesforce Acumatica Connector also stores Salesforce ID, product code, product name, price, and weight on Item Details. This guide focuses on product identity, item creation, stored identifiers, price-book relationships, and missing-item validation. Earlier articles cover setup, configuration, data flow, order import, and inventory allocation.

Salesforce Product Mapping Definition and Prerequisites

The Biz-Tech Services Acumatica Salesforce Connector uses Salesforce Store as the main configuration screen. Item Settings controls whether incoming products can create new ERP items, while Item Details shows synchronized product identifiers and supports synchronization in both directions.

Before mapping products, confirm the intended Salesforce Store record and review Item Settings. Import Item determines whether an unmatched incoming product may create a new item. Add Items in Inventory Sync enables synchronization with source products. Use Numbering Sequence for Product ID Generation can create unique product IDs for new products from a predefined numbering sequence.

The manual does not give a screen ID for Salesforce Store or its related processing screens. It also does not describe a separate item cross-reference screen. The documented identity rule is the Product SKU lookup against Inventory CD.

Salesforce Product Mapping Step by Step

Use this sequence to establish and verify the product relationship.

1 Open Salesforce Store and review Item Settings.

2 Decide whether Import Item should be selected. Select it only when the integration should create an ERP item for an unmatched source product.

3 Confirm that the Salesforce Product SKU contains the value that should match the Acumatica Inventory CD.

4 Decide whether Add Items in Inventory Sync should be selected for the products that need synchronization.

5 If new product IDs must be generated, enable Use Numbering Sequence for Product ID Generation and confirm that the required numbering sequence is defined.

6 Open Item Details and use Load Acumatica items to review the available ERP items.

7 Use Sync all from Salesforce when the documented requirement is to retrieve and create source products in the ERP.

8 Use Sync to Salesforce when the requirement is to create or update ERP items in the CRM platform.

9 Confirm Salesforce ID, product code, product name, price, and weight on Item Details after synchronization.

How Product SKU Matches Inventory CD

The mapping rule documented under Item Settings is direct. The connector searches Inventory CD using Salesforce Product SKU. If it finds a matching Inventory CD, it retrieves that item.

This rule connects a source product to an existing ERP item during import. The manual does not describe trimming, case conversion, leading-zero handling, or punctuation normalization. It also does not define which item wins if more than one record can satisfy the same SKU value.

Item Details displays product code in addition to Salesforce ID and product name, but the source does not say that product code replaces Product SKU in the Inventory CD lookup. Treat Product SKU as the documented identity input and use the other displayed values as review fields.

Import Item and Product ID Generation

When Import Item is selected, new items can be created in Acumatica according to the configured settings. The manual does not name an item type, Unit of Measure, product Item Class, default warehouse, or other item-creation defaults under Item Settings.

When Import Item is not selected, the connector prohibits import and creation unless the corresponding item already exists. If Inventory CD cannot be found from Product SKU, the documented error is The item {0} does not exist in the system. The placeholder represents the value supplied by the process.

Use Numbering Sequence for Product ID Generation applies to a new product ID rather than the Inventory CD lookup. The source says the option automatically generates unique product IDs from a predefined sequence. It does not explain where the sequence is selected, what field receives the generated ID, or how a generated ID interacts with an existing Product SKU.

Item Details and Stored Salesforce Identifiers

The Biz-Tech Services Salesforce Acumatica Integration uses Item Details to show the synchronized item Salesforce ID, product code, product name, price, and weight. Load Acumatica items retrieves ERP items and displays them in the table.

Sync to Salesforce creates or updates ERP items in the CRM platform. Sync all from Salesforce retrieves and creates source products in the ERP. Check All selects all displayed items and clears the selections when used again.

These actions document synchronization direction and stored identifiers, but the source does not define identifier precedence. It does not state whether Salesforce ID, product code, or Product SKU is authoritative after the relationship has been created, or how an ID conflict is resolved.

Cross References Aliases and Item Classes

Cross-Reference Options links selected entities between the two systems. The examples are Payment, Country, and Ship Via. A user selects the relevant checkbox and creates the mapping on the Cross-Reference tab.

The source does not identify products, Product SKU, Inventory CD, Salesforce ID, or product code as cross-reference entities. It does not document alternate IDs, aliases, manufacturer numbers, customer part numbers, or a lookup priority among multiple product identifiers.

Customer Class is documented for new customers created during order import. No product Item Class field or class-based item mapping rule is documented under Item Settings. Do not apply the customer setting to products or infer a product class from price-book membership.

Price Books and Product Relationships

Price Book Details loads source price books based on Last Imported Price Book Date. Salesforce Price Books can add products to a price book and define or update list price. The manual says products must first be included in the standard price book before they are added to another price book.

A source item that already exists in a price book must be brought into Acumatica by importing an order. During order import, the item is automatically added to the corresponding price book. This describes price-book membership after the item relationship is recognized; it does not define an additional SKU alias.

The Export Salesforce Price Books screen exports only items that have been updated or changed. Item Details and the SKU lookup remain the documented places for reviewing product identity, while price-book screens manage list price and membership.

Salesforce Price Book Details for product mapping

Unmapped Products and Validation Rules

The missing-item error provides the only explicit product-mapping validation message in the manual. It appears when Import Item is not selected and the Product SKU does not resolve to an Inventory CD.

The source does not identify an unmapped-product queue, Unmapped status, retry count, substitute-item option, or product-specific error inquiry. It also does not explain whether correcting a SKU permits the same retrieved order to be imported again or requires a new retrieval.

The Import Salesforce Orders screen retrieves and imports orders but does not document a line-level mapping error workflow. Therefore, do not invent a red-cross action, trace screen, or product exception list for this integration.

Import Salesforce Orders product mapping

Where to Check Your Work

The Biz-Tech Services Salesforce Acumatica Integrator provides these documented checkpoints for product mapping.

1 On Item Settings, verify Import Item, Add Items in Inventory Sync, and Use Numbering Sequence for Product ID Generation.

2 Confirm that Salesforce Product SKU matches the intended Acumatica Inventory CD.

3 Use Load Acumatica items on Item Details to confirm that the intended ERP record is available.

4 After Sync all from Salesforce, confirm that the expected item was retrieved or created.

5 After Sync to Salesforce, confirm that the source product was created or updated.

6 On Item Details, compare Salesforce ID, product code, product name, price, and weight with the intended product.

7 If the missing-item error appears, verify Product SKU and Inventory CD before changing other configuration.

8 For a price-book product, confirm standard price-book membership before adding it to another price book.

9 If a product identifier conflict exists, stop and validate the record manually because the manual provides no precedence rule.

Salesforce Product Mapping Frequently Asked Questions

What field matches a Salesforce product to an Acumatica item?

The documented lookup uses Salesforce Product SKU to search Acumatica Inventory CD. A match retrieves the existing item.

What happens when Product SKU does not match Inventory CD?

If Import Item is selected, the connector can create a new item. If it is not selected, the process displays The item {0} does not exist in the system.

Can the integration generate product IDs?

Yes. Use Numbering Sequence for Product ID Generation creates unique product IDs from a predefined numbering sequence. The manual does not identify the sequence field or explain how the generated ID affects Product SKU.

Does the Cross Reference tab map product aliases?

The Biz-Tech Services Acumatica Salesforce Integration documents Payment, Country, and Ship Via as examples. It does not identify product aliases, Product SKU, Inventory CD, Salesforce ID, or product code as cross-reference entities.

Does Item Class control product mapping?

No product Item Class field is documented under Item Settings. Customer Class applies to customer creation and should not be treated as an item setting.

Where can I see the synchronized product identifiers?

Item Details displays Salesforce ID, product code, product name, price, and weight for synchronized items.

How are products connected to price books?

Products must be in the standard price book before another price book. Products already in a source price book are brought into the ERP through order import and added to the corresponding price book.

Where can I review unmapped products?

The manual does not name an unmapped-product queue or product exception inquiry. Review Item Settings, Product SKU, Inventory CD, Item Details, and the documented missing-item error.

Work With Biz Tech Services Salesforce Mapping

A reliable product relationship starts with a consistent Product SKU and Inventory CD, then uses Item Details to confirm Salesforce ID and the other stored product values. Import Item and product-ID numbering determine how new products are handled, while price-book screens manage membership and list price.

For help configuring and validating the Biz-Tech Services Acumatica Salesforce Integrator, visit https://biz-techservices.com to learn more about Biz-Tech Services and schedule a personalized consultation.


How to Map Inventory IDs for Acumatica Imports with Biz-Tech AI Analyst

Biz-Tech AI Analyst can design an Acumatica Import Scenario from an attached Excel or CSV file, including the mapping from spreadsheet columns to the selected entry screen. For an inventory import, the important review is whether the file's item identifier points to the intended Acumatica Inventory ID. The product page says AI Analyst checks key and required fields, then shows its proposed mapping for approval. Your team still prepares and imports the data.

That approval step is where a supplier SKU, legacy product code, or blank identifier should be resolved. AI Analyst's published description does not promise automatic SKU matching or item creation from an unmatched code. Treat the proposal as a design to inspect, using a small sample file before it is used with a full catalog.

What AI Analyst Builds for an Inventory Import

A user attaches an Excel or CSV file and describes the intended import in the AI Analyst screen. The assistant selects an Acumatica entry screen, maps file columns, checks required fields and keys, and presents a plain-language proposal. The preview identifies the import mapping and any limitations or Heads up notes. The user can request changes; the Data Provider and Import Scenario are created only after approval.

1 BizTech AI Analyst

Acumatica uses the Data Provider to define the external file's columns and the Import Scenario to map those columns to fields on a data-entry form. The scenario is specific to the selected form and the file schema. A design for new stock items therefore needs a different review from a design that updates existing items or imports transaction lines.

Inventory ID Mapping at a Glance

Use this sequence while reviewing an AI Analyst proposal:

Identify the source column that holds the item's code. Record whether it contains Acumatica Inventory IDs, supplier SKUs, customer part numbers, or mixed values.

Confirm the selected Acumatica entry screen and the target field for that source column. The proposed destination must match the job: item maintenance, a document line, or another entry form.

Ask which source columns satisfy the key and required target fields. A description or display name should not silently stand in for the item identifier.

Separate unmatched, duplicate, or ambiguous codes in the sample file for a human decision. Do not approve an assumed match when two Acumatica items could fit.

Approve the mapping only after the sample rows show the intended target. The team then uses Acumatica's Prepare and Import actions and reviews the results.

Define What the Source Item Code Means

Start with the actual header and values in the spreadsheet. A column named SKU may be your company's Inventory ID, a vendor's number, or a code left over from another system. Those meanings lead to different mappings. Keep a few representative rows that include a known item, a code that does not exist in Acumatica, a blank value, and a duplicate. This is an editorial test set for reviewing the proposal, not a claim that AI Analyst classifies those cases automatically.

Acumatica identifies stock and non-stock items by Inventory ID. Its Stock Items (IN202500) and Non-Stock Items (IN202000) forms can also hold alternate IDs on the Cross-Reference tab. If the source file uses an alternate ID, confirm how the chosen import form and scenario will interpret it. An alternate ID that works in one Acumatica entry field does not by itself prove that this import design will resolve it correctly.

Check the Target Screen, Keys, and Required Fields

The target screen determines what a row will do. An import to Stock Items (IN202500) can maintain stock-item records; a transaction-line import has a different destination and document context. Ask AI Analyst to show the target screen and each source-to-target field pair in its proposal. Confirm whether the job is creating items, changing existing items, or referencing items on another record before approving the design.

The product page says AI Analyst checks key and required fields, but it does not publish a universal field list for inventory imports. Your tenant's configuration, custom fields, and chosen screen can change the requirements. Review the proposal against the actual Acumatica form. If the key is missing or points to the wrong spreadsheet column, revise the design before a Data Provider and Import Scenario are built.

AI Analyst works from a catalog of fields and relationships in the customer's Acumatica environment, including fields added by published customizations. This gives the proposal a tenant-specific basis. It does not replace the team's decision about which external code identifies the right product.

Handle Unmatched and Duplicate Items Before Approval

For each source code that lacks a clear match, decide whether it represents a new item, a missing cross-reference, or an error in the file. Record that decision outside the import proposal if needed. The AI Analyst product description does not specify an unmatched-item queue, a duplicate-SKU rule, or an automatic alias resolution process, so those behaviors should not be assumed.

Review a small file first. Check leading zeros and punctuation in codes, repeated identifiers, and any rows that combine stock and non-stock products. These are practical file checks, not AI Analyst features promised by the product page. If a sample row could update the wrong item, correct the source file or mapping proposal and test again.

Prepare, Import, and Inspect the Result

Approval creates the Data Provider and Import Scenario. It does not run the import. On Import Scenarios (SM206025), the team can inspect the selected provider, target screen, and mapping. On Import by Scenario (SM206036), Prepare loads rows for review without importing them. The Prepared Data area shows errors on affected rows. Import is a separate action that processes the prepared rows.

Run the sample through Prepare first, inspect the selected target values and errors, and correct the file or scenario before importing. After Import, check the target Acumatica records against the sample. A successful processing status is useful, but the business check is whether the intended Inventory ID was created, updated, or referenced. Keep the approved proposal and the sample results for the next file revision.

Where to Check Your Work

AI Analyst proposal: review the entry screen, column mapping, limitations, and approval record; confirm the key and required-field decisions before approval.

Data Providers (SM206015): confirm the attached file schema and source columns.

Import Scenarios (SM206025): inspect the scenario's target form and Mapping tab.

Import by Scenario (SM206036): use Prepare to review rows and the Error column before Import.

Stock Items (IN202500) or Non-Stock Items (IN202000): compare the resulting item with the source sample when those forms are the intended target.

Inventory ID Import Mapping: Frequently Asked Questions

Does AI Analyst import the inventory records for me?

No. Biz-Tech's product page says AI Analyst creates the Data Provider and Import Scenario after approval. Your team controls Prepare and Import.

Can a supplier SKU be used as the Acumatica Inventory ID?

That is a mapping decision, not a published automatic rule. Confirm whether the source code is the intended Inventory ID or an alternate ID, then test the proposed mapping on the selected entry screen.

What if a source item has no match?

The product description does not define an automatic unmatched-item workflow. Hold that row for a human decision about creating an item, correcting the file, or maintaining an appropriate cross-reference.

Will AI Analyst catch duplicate SKUs?

No duplicate-SKU behavior is documented. Put repeated and ambiguous codes in the sample review and verify the resulting mapping before a full import.

Where do I see import errors before records change?

Acumatica's Import by Scenario (SM206036) form lets the team run Prepare and review prepared rows and errors before choosing Import.

Can I change the mapping before it is built?

Yes. AI Analyst presents the proposal in plain language, accepts refinements in the conversation, and builds only after the user approves it.

Review the Mapping with Your Team

The safest starting point is one representative file and a precise definition of each item identifier. Let AI Analyst propose the scenario, then review the key, destination fields, and exceptions with the people who own the item catalog. They retain the final control over Prepare and Import.

Bring a sample inventory file to a Biz-Tech AI Analyst demonstration. Visit https://biz-techservices.com to discuss the mapping and approval steps with Biz-Tech Services.

Sources: Biz-Tech Services, Biz-Tech AI Analyst, https://biz-techservices.com/biz-tech-ai-analyst; Acumatica, Import Scenarios (SM206025), https://beacon.acumatica.com/r/Form-Reference-Guide/Integration-Forms/Import-Scenarios; Acumatica, Import by Scenario (SM206036), https://beacon.acumatica.com/r/Form-Reference-Guide/Integration-Forms/Import-by-Scenario; Acumatica, Stock Items: Identifiers of Items, https://beacon.acumatica.com/r/Inventory-Management-Guide/Creating-Stock-Items/Stock-Items-Identifiers-of-Items.


How to Map PayPal Invoice Lines to Acumatica Items

The PayPal integration guide does not document a way to map PayPal invoice lines to Acumatica Inventory IDs, stock items, or non-stock items. Its documented workflow creates a PayPal invoice from an Acumatica sales order, accounts receivable invoice, or payment amount and then tracks the resulting payment at the document and application level.

The Biz-Tech Services PayPal Acumatica Connector sends payment requests and stores PayPal invoice identifiers, URLs, statuses, transaction IDs, refund IDs, and paid amounts. The source does not name a SKU, Inventory ID, item class, item alias, or product cross-reference field. Item mapping therefore remains outside the documented PayPal customization workflow.

What the PayPal Connector Sends from Acumatica

The Biz-Tech Services Acumatica PayPal Connector creates a PayPal payment request from one of three Acumatica entry points. A user can start from Sales Orders, from an Invoice, or from Payments and Applications. All three paths create or use an AR Payment, send a PayPal invoice to the customer's email, and place the payment on Hold with a Sent status.

From Sales Orders, Create Payment reads the order total, currency, and customer details. After Cash Account and Payment Reference are supplied, Request PayPal Payment creates an AR Payment linked to the order and stores PayPal Invoice ID, Invoice URL, and Invoice Number on the payment.

From the documented Invoice workflow, Request PayPal Payment creates a payment pre-applied to the invoice. The PayPal invoice amount matches the outstanding balance. The guide does not state that Acumatica invoice lines are copied, matched, or recreated as PayPal invoice lines.

10 Sales Order Payment

PayPal Invoice Line Mapping at a Glance

The source supports the following conclusions about the boundary between item records and PayPal payment requests.

1. Sales Orders can supply order total, currency, and customer details to the payment request

2. An accounts receivable invoice can supply its outstanding balance to the PayPal invoice amount

3. A standalone payment can supply a customer, PayPal payment method, email, amount, and optional description

4. Orders to Apply and Documents to Apply can associate a payment with a Sales Order or Invoice

5. PayPal fields are stored on the AR Payment and related ARAdjust and SOAdjust application records

6. No documented field maps a PayPal line description or product code to an Acumatica item

Sales Orders Supply Totals Rather Than Documented Item Mappings

The Sales Order path starts on Sales Orders. Create Payment reads the order total, currency, and customer details, and the resulting AR Payment remains accessible from the order's Payments tab. The source describes the payment link to the order, not a line-by-line link to inventory records.

No PayPal line-item table, Inventory ID field, quantity field, unit price field, or product identifier is listed in this workflow. The documentation also does not say whether the customer sees one summarized PayPal invoice line or several lines. Any such behavior would need confirmation outside the supplied guide.

The payment application preserves a document relationship, but a document relationship is not an item cross-reference. The source does not provide evidence that changing an Acumatica sales order line changes an already sent PayPal invoice or that PayPal can update an inventory item.

AR Invoices Supply the Outstanding Balance

The Invoice path is designed for billing that has already been posted. Request PayPal Payment creates a payment pre-applied to the invoice, sends the PayPal invoice, and puts the payment on Hold. The source states that the PayPal amount matches the outstanding balance on the AR invoice.

Outstanding balance is the only invoice-content rule documented for this path. The guide does not mention invoice-line descriptions, Inventory IDs, quantities, item classes, tax categories by line, discounts by line, or line-level references in the PayPal request.

The Payment Method ID becomes locked once an invoice has been sent. That rule protects the PayPal payment method assignment; it is not an item-mapping lock or a line validation rule.

Standalone Payments Have No Required Item Context

Payments and Applications supports a standalone payment, such as a deposit that is not tied to a specific document. The user selects the customer and PayPal payment method, reviews PayPal Customer Email, enters the payment amount and an optional description, and sends the request.

11 Payments And Application

A payment can optionally be applied to a Sales Order or Invoice through Orders to Apply or Documents to Apply. The source does not require an Inventory ID or item line for a standalone request. This confirms that the documented PayPal process operates at the payment and document level.

The optional description is not defined as a SKU, alias, inventory description, or matching key. The guide provides no rule for using it to identify an Acumatica item.

Cross References Aliases and Unmapped Items Are Not Documented

The Biz-Tech Services PayPal Acumatica Integration documentation contains no item cross-reference screen, alias table, SKU lookup, Inventory ID field, product-code mapping, item-class default, or unmapped-product queue. It does not describe any record that pairs a PayPal value with an Acumatica item.

No behavior is defined for an unknown PayPal product, duplicate product code, blank item value, different letter case, leading zeros, stock versus non-stock items, or multiple external aliases for one local item. The source also does not describe creating inventory records from PayPal data.

The only related line records named by the guide are ARAdjust and SOAdjust. The PayPal custom fields are available on those applied-to lines so payment status information remains consistent across related records. The guide does not identify either record as an invoice-item mapping table.

PayPal Fields Track Payment Status Not Inventory Items

The custom fields added to the AR Payment screen are PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Status, PayPal Invoice Number, Transaction ID, PayPal Invoice URL, Refund Number, and PayPal Paid Amount. Each field supports payment delivery, status checks, or refund tracking.

The processing screen also displays Payment Ref, Customer, Customer Email, Currency and Amount, Sales Order, Invoice Number, PayPal Invoice Number, PayPal Status, and Transaction ID. None of the documented columns identifies an item, SKU, quantity, warehouse, item class, or product alias.

PayPal Invoice Status can be Sent, Partially Paid, Paid, Cancelled, Refunded, or Partially Refunded. These statuses govern the AR Payment lifecycle and do not validate invoice-line-to-item matching.

Validation Rules Apply to Payments and Requests

The guide documents validation and troubleshooting for PayPal credentials, customer email, invoice status, release eligibility, and refunds. Test Connection validates the API credentials on Payment Methods. A Customer Payment Method supplies the customer's PayPal email address.

A payment must not have been sent previously before Send PayPal Request is used. A payment still in Sent status cannot be released because PayPal has not confirmed payment. Refunds require a Paid PayPal state and a fully released local payment. These are payment-level rules.

The source gives no item-mapping validator, line-error field, item exception log, or rule that blocks a PayPal request when an Acumatica invoice contains a particular item. It does not provide an item reconciliation screen after the request is sent.

Where to Check the Documented PayPal Data

The Biz-Tech Services PayPal Acumatica Integrator exposes payment and document evidence in the following documented screens and fields. None is identified as an item-mapping review.

1. On Sales Orders (SO301000), review the Payments tab and linked AR Payment

2. On Payments and Applications (AR302000), review PayPal Customer Email, PayPal Invoice ID, PayPal Invoice Number, PayPal Invoice URL, and PayPal Invoice Status

3. Review Orders to Apply and Documents to Apply for document-level applications

4. On the Check PayPal Payment Status processing screen, review Sales Order and Invoice Nbr links

5. Review Currency and Amount, PayPal Status, Transaction ID, and PayPal Paid Amount for payment reconciliation

6. Treat the absence of Inventory ID, SKU, quantity, item class, and alias fields as a documented scope boundary

PayPal Invoice Line Mapping Frequently Asked Questions

Does the PayPal integration map invoice lines to Inventory IDs?

The Biz-Tech Services Acumatica PayPal Integration guide does not document that capability. It describes totals, outstanding balances, payment applications, and PayPal status fields, but it names no Inventory ID or item-mapping field.

Does PayPal receive the sales order line items?

The source says the Sales Order workflow reads the order total, currency, and customer details. It does not say that individual order lines are sent.

What amount is used when the request starts from an AR invoice?

The PayPal invoice amount matches the outstanding balance on the AR invoice. No line allocation rule is supplied.

Can an item SKU be stored in the payment description?

The standalone payment accepts an optional description, but the guide does not define it as a SKU, item alias, or product-matching field.

Are ARAdjust and SOAdjust item mapping records?

The source says PayPal fields are available on ARAdjust and SOAdjust applied-to lines to keep status information consistent. It does not describe them as item cross-reference records.

Does the connector create missing Acumatica items from PayPal?

No item-creation workflow is documented. The customization creates and updates AR Payments and PayPal invoices, not inventory records.

Can item classes or aliases control PayPal invoice content?

The guide does not mention item classes, item aliases, alternate product IDs, or rules that use them to build a PayPal invoice.

Where should item mapping be validated?

The supplied PayPal documentation gives no item-mapping validation screen. Item accuracy must be established in the source Acumatica document or another documented product process before a PayPal request is created.

Work With Biz Tech Services on PayPal Payment Requests

The documented PayPal customization sends document-level payment requests and tracks their status through AR Payment fields and application records. It does not define product, SKU, item-class, alias, or line-level Inventory ID mapping.

If your team needs help confirming the boundary between Acumatica document data and PayPal payment requests, the Biz-Tech Services Acumatica PayPal Integrator can support your implementation. Visit https://biz-techservices.com to contact Biz-Tech Services or schedule a personalized demonstration.

Check the video lesson here: https://www.youtube.com/watch?v=wkjPKdLzv2M


Privacy Preference Center