A unique identifier used to authenticate a system or user when connecting to SyncSpider’s API or to external endpoints. Ensures secure communication and access control.
An attribute is a defined characteristic or property of a data entity—such as a product, customer, or order record used to describe, classify, or filter that entity within the system. For example, a product might have attributes like color, size, material, weight, or SKU. In the context of SyncSpider (and its DataHub or integration workflows), attributes serve as fields or parameters that can be mapped, transformed, filtered, and synchronized across connected systems. Proper management of attributes ensures consistency, accuracy, and clarity in data exchange.
A feature in SyncSpider that automatically retries a task or workflow if it fails or hits an error, helping maintain data flow continuity without manual oversight.
(Synonyms: Process Automation, Workflow Automation)
In the SyncSpider context, automation refers to configuring tasks and workflows within the platform that remove manual data entry, synchronize systems, and trigger actions automatically, from product updates to order processing and reporting workflows.
(Synonym: Bulk Operations)
The execution of operations on large sets of records (e.g., thousands of products, orders, or customers) in a single run rather than one-by-one. Enables efficient data handling in high-volume use cases.
A pre-built integration interface within SyncSpider that allows you to connect a specific system (ERP, CRM, marketplace, or eCommerce platform) quickly with minimal custom coding. Connectors simplify the setup of data flows between systems.
A preconfigured setup in SyncSpider that defines how a specific external system (ERP, CRM, marketplace) will connect, including endpoints, data flows and mappings — speeding up integration deployment.
User-defined attribute within SyncSpider’s DataHub (or workflow) that allows companies to extend the data model beyond standard fields (e.g., adding “Brand ID” or “Warehouse Region” to products).
A centralized schema within SyncSpider designed to manage all customer data, including accounts, roles, addresses, and related metadata.
A centralized repository where structured data from multiple sources is stored and used for reporting, analytics or further processing. In SyncSpider’s context, the DataHub serves this purpose for product, order, and customer data.
A core module of SyncSpider: a centralized data platform for collecting, storing, transforming, and exporting large volumes of business data (products, customers, orders, suppliers) from multiple sources.
Within the DataHub module, an “Entity” is a defined data object type (for example Products, Customers, Orders) that allows you to structure, classify, and manage your data inside SyncSpider.
A logic component within a workflow or in DataHub that allows you to select only certain records based on specified criteria (e.g., only customers in Germany, only orders above a certain value). Filters help refine and control data flows.
The ability of SyncSpider to connect both cloud-based systems and on-premise systems (databases, local ERP) in the same workflow, enabling seamless hybrid architecture.
A data import method where only new or changed records (since the last run) are imported into the system rather than all records every time. Reduces processing time and system load.
The process of linking two or more software systems using SyncSpider so they exchange data, trigger workflows, and stay synchronized (for example ERP to e-commerce store, PIM to portal). Without integrations, automation and real-time data flows are not possible.
A defined path within SyncSpider that shows how data moves from source → transform → destination, including triggers, mappings, and filters. Essentially, the “workflow map” of a business process.
The timing configuration for when SyncSpider tasks or workflows run, for example, every 5 minutes, hourly, or daily. Ensures automated tasks are executed at set frequencies without manual start.
In the DataHub context, an “Item” is a singular data record within an Entity, for example, one specific product, one order, or one customer record.
A connector designed to integrate older systems (e.g., on-premise databases, legacy ERP) into SyncSpider when standard APIs are unavailable. Provides compatibility for enterprise setups.
A detailed record within SyncSpider of each task or workflow execution: time started, number of records processed, errors encountered. Critical for troubleshooting and compliance.
The visual or configuration interface in SyncSpider where fields from the source system are matched to fields in the destination system (e.g., “SKU” → “ItemCode”). Ensures data aligns correctly.
Software or infrastructure in the integration architecture (including within SyncSpider) that sits between systems and enables communication, translation, synchronization, and routing of data between applications (such as ERP, CRM, portals).
A functional component or building block of the SyncSpider platform (e.g., the DataHub module, Task module, Portal module). Each module provides specific capabilities in the ecosystem.
In SyncSpider metrics, an “operation” often refers to the processing of a single record within a task (e.g., updating one product or one order). This is useful for monitoring usage, load, and performance.
A business document or transaction indicating a customer purchase request. In SyncSpider workflows, orders can be imported, validated, routed, synced to ERP, exposed via portal, and tracked.
A dedicated module or centralized hub within SyncSpider is designed to collect, manage, and monitor all order-related data from various sources in one unified place. OrderHub enables businesses to synchronize incoming orders from multiple sales channels, apply validation rules, route orders to the appropriate back-office or fulfillment systems (e.g., ERP or warehouse), and track the order lifecycle through status changes. By placing all orders into a single hub, it supports efficient orchestration of order workflows, simplifies troubleshooting and reporting, and ensures that every order is visible across platforms.
A user interface (often web-based) provided by SyncSpider for customers, sales agents or internal users to interact with the system (e.g., view product catalogs, place orders, track shipments). The B2B Portal by SyncSpider is an example of this term in action.
A series of steps or operations (often automated via SyncSpider) carried out to accomplish a business objective, for example, the process of order intake → validation → fulfillment → invoice.
A central schema for product data within SyncSpider, managing attributes, media, pricing, and other key product-related information.ProductHub serves as the single, authoritative source for all product records, ensuring that every connected system, including ERP, PIM, eCommerce, and B2B portals, accesses consistent and up-to-date data. It simplifies catalog management, supports multilingual and multi-currency setups, and maintains structured, validated product information across channels.
A scheduled execution of a task in SyncSpider at the set interval, performing defined operations (imports, exports, data sync) according to configuration.
The action of ensuring data in two or more systems is aligned and up-to-date (for example, product details in your ERP and portal, or order status in back-office and front-end). Synonym: Sync. Ensures “single source of truth”.
A unit of work defined inside SyncSpider that executes an action, for example, “Import orders from Shopify”, “Update stock in ERP”, “Export product data”. Tasks are scheduled or triggered and are the building blocks of workflows.
The configuration of what each user in the SyncSpider platform can view or manage. For example: administrator, integration-manager, viewer. Helps segment access for security and governance.
A supplier or partner system whose data (products, inventory, shipments) is integrated via SyncSpider into your ecosystem. Vendors supply data to you (or you to them) and often feed into B2B portals, marketplaces, or e-commerce platforms.
In the DataHub module, a “View” defines how data in an Entity is presented (e.g., table layout, list view, filtered view). Views help you manage how items in an entity are shown and accessed.
The mechanism by which SyncSpider processes inbound webhooks: validating payload, parsing data, triggering workflows, and sending responses back if needed. Ensures reliable event-driven integrations.
An event-based trigger that kicks off a workflow in SyncSpider not on schedule but when a specific event happens (e.g., new order created, customer updated). Provides real-time data reaction.
A configured sequence of tasks, filters, mappings, and connectors inside SyncSpider that defines the logic and path of data from one system to another, for example: “When a new order arrives → map fields → validate data → send to ERP → notify customer”.
In multi-client setups, a “workspace” or “tenant” represents a separate environment or partition in SyncSpider for a specific client, brand or division, ensuring data isolation and configurability.