Glossary
The terms you meet in the portal, in plain language. Where a word has a specific meaning in Unifd that differs from everyday use, that is called out.
Activity
Section titled “Activity”The page listing every recent sync run across your pipelines. Your home page after signing in. See Sync runs.
A batch of records within a step. Large amounts of work are split into chunks so one bad record does not stop everything else. A run’s detail panel reports how many chunks succeeded, were partial, failed or were skipped.
Cash receipt
Section titled “Cash receipt”A record of a payment taken on your storefront, written into your source system against the matching order. See Cash receipts.
Company
Section titled “Company”A trade account customer — a business that buys from you, rather than an individual shopper. Shown on the Companies tab, and as B2B in an order’s Type column. A company has one or more locations. See Companies.
Data type
Section titled “Data type”What kind of data a pipeline moves — products, inventory, orders,
companies, fulfilments, gift_cards, cash_receipts or loyalty. It decides
which tabs and settings the pipeline has.
The phase of a run that works out which records actually changed, so only those are sent onward. It is why a routine sync writes far fewer records than it read.
Destination
Section titled “Destination”See Target.
Fulfilment
Section titled “Fulfilment”Despatch information — that an order has shipped, and its tracking number — flowing from your source system back to your storefront. See Fulfilments.
Health
Section titled “Health”On the Products tab, whether the copy of a product on your storefront is current and correct — OK, Changed or Failed. Separate from Push, which is about whether it was ever sent at all. See Statuses.
Integration
Section titled “Integration”A connected system — your source system or your storefront. An integration holds the connection details; it does not move any data by itself. That is a pipeline’s job. See Integrations.
Location
Section titled “Location”For stock, a place where stock is counted or sold. For a trade account, a delivery or billing address — the Locations column counts them, and an account needs at least one to be ordered against.
Location mapping
Section titled “Location mapping”A pairing between a warehouse in your source system and a location on your storefront, so stock counted in one appears against the other. Set on an inventory pipeline’s settings. See Pipeline settings.
Mapping
Section titled “Mapping”The field-by-field rules that turn a record in your source system into a record on your storefront — for example which source field becomes the product title. Edited in the Mapping Editor, normally set up with the Unifd team.
Market
Section titled “Market”A storefront market, used to route orders and to scope an orders pipeline to a region. Read from your storefront as a resource.
A named stage of a run, shown with a letter badge in a run’s detail panel. A product or stock sync has five, in this order: Extract, Prune, Diff, Resolve and Distribute. Which phase failed tells you where the problem is: Extract points at your source system, Distribute at your storefront. Not every kind of run has phases — some list their steps flat instead. See Sync runs.
Pipeline
Section titled “Pipeline”A flow that moves one data type from one integration to another, on a schedule. Pipelines are the unit you monitor and run. See Pipelines.
Pipelines are one-directional. Products and stock flow from your source system to your storefront; orders flow back the other way. A pipeline’s Source and Target tell you which.
Price list
Section titled “Price list”Pricing held on your storefront for trade accounts. Read from your storefront as a resource and used through a catalogue.
A phase of a run, shown as P, concerned with records that are no longer in your source system.
Sending a record to your storefront. On the Products tab, Push is also the column saying whether a product has ever been sent: Pushed or Not pushed.
Resources
Section titled “Resources”The reference lists Unifd reads from a platform and your pipelines then use: Locations, Pricelists, Publications, Catalogues and Markets. An integration’s detail page shows a count against each and has a Sync now button to re-read them. Some screens cannot offer you choices until resources have been synced. See Integrations.
Rows in / Written / Failed
Section titled “Rows in / Written / Failed”The three figures reported for a run. Rows in is how many records were read from the source, Written how many reached the destination, and Failed how many did not. Rows in equal to Written with none failed is a clean run.
One execution of a pipeline, successful or not. Every run is listed on
Activity with its outcome, duration and figures, and labelled by its kind —
for example product-sync, inventory-sync, fulfilment-delta-poll or
cash-receipt.
Skipped
Section titled “Skipped”A step that had nothing to do. Normal, and not a failure — a run can be a Success with several skipped steps.
Schedule
Section titled “Schedule”The rule saying when a pipeline runs by itself. A pipeline can have none, one or several. See Schedules.
Source
Section titled “Source”The integration a pipeline reads data from.
Source ID
Section titled “Source ID”The identifier a record has in your source system — for example a product code. The most reliable thing to search by, because it does not change when a title is edited.
Source system
Section titled “Source system”The system where your data is managed — your ERP or merchandising system. Unifd treats it as the truth and copies from it.
One unit of work inside a run. Steps are grouped into phases. A run’s row on
Activity summarises them as, for example, 3 ok · 1 failed · 4 steps.
Source order
Section titled “Source order”The order a gift card was bought on, or the storefront order a payment or despatch belongs to.
Storefront
Section titled “Storefront”Where your customers buy — your online shop. Usually the target of your products and inventory pipelines, and the source of your orders pipeline.
Target
Section titled “Target”The integration a pipeline writes data to. Also called the destination.
Trigger
Section titled “Trigger”How a run started. cron means a schedule started it; manual means somebody
did, with Sync now. Shown in a run’s detail panel.
Workspace
Section titled “Workspace”One set of integrations, pipelines and data, with its own name. Every list in the portal shows only your currently selected workspace, and the line under the switcher tells you how many you can reach. Switch with the workspace switcher at the top of the sidebar.
This glossary covers what is in the merchant portal today. If you meet a term in the portal that is not here, ask your Unifd contact and we will define it and add it.