This is a step-by-step walkthrough for a user to set up a data integration from NetSuite to Ekyam, culminating in a live data synchronization.
1

STEP 1

Select the ConnectorSelect the NetSuite Connector from the Ekyam Integration Options. Below is the screen that appears:image (28) 1.png
2

Step 2

Check AuthenticationOn clicking the Netsuite connector, the user needs to fill the keys in the below screen to get the system connected to Ekyam Platform.image (29) 1.png
3

Step 3

Map Your Data (Universal Reader):Click on Map Configurationsimage (35).pngAfter clicking on the Map Configurations, the screen below appears. The Products and Shipments data can be pulled using NetSuite’s end-points.Image(36) PnThe user needs to click on the Verify button, to come to the below screen.image (37).png
Note: The keys are mapped using AI,  that validates the client’s keys.
The data pulled from the Products and Shipments is then converted  to Ekyam Data Standards.Image(38) PnHowever, the drop down mapping may differ for different systems.Group 2085666843.png
4

Step 4

Configure Data flows- Click on the Edit configurationImage(32) PnAfter clicking on Edit configuration, below screen appears:Image(33) PnThe above screen shows that the data has been configured. Then we see an “On sign” (or a green/active indicator) on a synchronization step like “Shipment Sync” in a workflow diagram, it precisely implies several crucial operational statuses:
  1. Active Connectivity: It confirms that the connection between Netsuite (the source system for shipment data) and the Ekyam platform is live and operational. Data is actively flowing or ready to flow.
  2. Successful Configuration & Setup: This indicator signals that all the necessary groundwork has been completed for this specific data flow. This includes:
    • Authentication: Ekyam has successfully authenticated with Netsuite.
    • Field Mapping: The critical step of field mapping has been done. This means Ekyam understands exactly which data fields from Netsuite’s shipment records correspond to the fields required by the next system in the chain (Whiplash, in this case). Workflow Logic:.
  3. Data Synchronization is Live: The “On sign” means that the shipment products (or rather, the shipment data containing product information) are actively being synced from Netsuite to the Ekyam platform, and then subsequently processed and delivered to the intended destination (Whiplash). 
    However, with the Ekyam’s Real-time Webhook/Event listening, the data can be pulled in real-time. This robust framework ensures that when critical business events occur within Ekyam, external applications are notified and updated in near real-time, facilitating immediate response such as inventory synchronization or order fulfillment. Webhooks
    1. Developers register webhook endpoints for the events they want to receive.
    2. Ekyam publishes events to Kafka topics.
    3. A dedicated webhook consumer service reads from Kafka and delivers events to the registered webhooks.
    4. Robust Retry Logic: Exponential backoff, maximum retry attempts, and a Dead-Letter Queue (DLQ) for failed deliveries.
    5. DLQ Monitoring: Developers can view and manage messages in their DLQ via the Developer Portal.
    6. Alerting: Notifications for DLQ events.
5

Step 5

We do not have any writer mapping for Netsuite.
6

Step 6

Workflow of NetSuiteThis diagram illustrates a streamlined and automated order fulfillment and inventory management process. It connects the core business management (Netsuite) with the physical fulfillment (Whiplash) and the online sales channel (Shopify). Let’s break it down:Image(34) PnCore Systems Involved:
  1. Netsuite: This represents the Enterprise Resource Planning (ERP) system. Netsuite is a comprehensive cloud-based business management software that integrates financial management, ERP, CRM, and e-commerce functionalities. 
  2. Whiplash: This refers to Whiplash Fulfillment, which is a leading e-commerce fulfillment and warehouse management (WMS) provider. It handles the physical storage, picking, packing, and shipping of products for online retailers.
  3. Shopify: This is a popular e-commerce platform where online stores are built and customer orders are placed. 
Data Flow Explained
  1. Netsuite → Shipment Sync → Whiplash:
This flow signifies that once an order is processed or marked for fulfillment within Netsuite (the ERP), the relevant shipment information is sent to Whiplash. This shipment data would typically include details necessary for the warehouse to fulfill the order, such as:
  • Order details (items, quantities, customer address)
  • Shipping method
  • Customer information
  • Any specific fulfillment instructions
This ensures that Whiplash receives all the necessary information to pick, pack, and ship the customer’s order accurately and efficiently.
  1. Whiplash → Inventory Sync → Shopify
As Whiplash fulfills orders (shipping items out) or receives new stock (inventory coming in), the actual, real-time inventory levels stored in Whiplash’s WMS are updated. This crucial inventory data is then synchronized back to Shopify.