Keeping Product Masters in Sync Between Your ERP and EDGEBIC

Keeping product masters in sync between an ERP and EDGEBIC comes down to a stable item identifier, case-insensitive matching, and a mask that writes only the columns the ERP should own. Re-importing the full item list is safe because matched rows come back Reused and untouched, changed rows come back Updated, and blank cells preserve the values you maintain inside EDGEBIC. The sync is a habit, not a project.

EDGEBIC by User Solutions matches items on a natural key rather than an internal row number, which is what makes a repeatable product refresh reliable. This post covers how the matching works, how to read the outcomes, and how to split which system owns which field. The wider integration model is in the EDGEBIC ERP integration overview.

The identifier is the natural key

Every product import matches on the item identifier, treated as a natural key and matched case-insensitively. BRK-200 in a file finds brk-200 in the database, so everyday case variation between departments never creates duplicates. Because matching is on the identifier and not on an internal row number, the same item list re-imports cleanly every week, each row landing on the correct existing record.

The one thing matching cannot absorb is a genuinely different string. An extra space, a swapped separator, or a leading zero present in one export and absent in another reads as a new identifier and creates a new item. A revision suffix raises the same question on purpose rather than by accident, and whether a revision should create a new product or update the existing one is worth settling before the first refresh. Keeping the master clean is therefore an upstream discipline: choose one canonical form for the part number in the ERP and export it consistently.

Reading the four outcomes

Every row of a product import returns exactly one outcome, and reading the mix tells you the master's health:

• Created. The identifier was new; a product was added.
• Updated. The identifier matched and at least one mapped value differed; the record was refreshed.
• Reused. The identifier matched and nothing changed; the record was left alone.
• Failed. The row was rejected, with the reason recorded in the per-run log.

A healthy weekly product import is mostly Reused, a few Updated, and a handful of Created. A sudden surge of Created rows on a list you expected to match is the classic sign of an identifier drift, worth investigating before it multiplies.

Splitting who owns which field

The most useful sync habit is deciding which system owns which attribute, then building the mask to respect that split. Two behaviors make this clean:

• A mask only writes the columns it maps. If the product mask carries identifier, description, and cost but not lead time, every import refreshes descriptions and costs from the ERP and never touches the lead times you maintain in EDGEBIC.
• Blank cells preserve values. On an update run, a blank cell keeps the existing value rather than wiping it, so even a sparse export cannot erase a field it simply left empty. A zero, however, is a value, so leave a column out rather than filling it with zeros you do not mean.

The practical rule: map the columns the ERP should own, leave out the columns EDGEBIC should own. That gives a clean split of authority, ERP for commercial data like descriptions and costs, EDGEBIC for scheduling attributes, with neither side overwriting the other.

Where product data feeds the schedule

Product master data is foundation for the schedule but does not drive it alone. The item identifier is what routings and orders attach to, so a stable master keeps routings pointed at the right products and orders resolving to the right items. Costs feed the cost rollups on reports; lead times and other attributes inform planning. The engine that consumes all of this is mapped in the EDGEBIC product overview.

Fitting product sync into the weekly routine

Product masters are the first import in the standard order, before work centers, routings, and orders, because downstream data attaches to items. In practice the product refresh is the fastest step, because a stable master is mostly Reused and clears in seconds. The full order of operations is in scheduling a nightly ERP export and import routine, and the exact columns each file should carry is in which ERP fields EDGEBIC needs to schedule.

Get your identifiers right once

A clean, consistent item identifier is the whole foundation of a durable sync. Export your item list, check that the identifiers are canonical, and bring the file to a demo to map it live and watch the Reused, Updated, and Created counts on a real refresh. Per-ERP guides like NetSuite and Acumatica show the same product-import step in those systems' terms.