Articles in this section

Front Systems - Nedap/!DCloud Integration

Avatar
Divya Ranamalla
  • Updated
Follow

Front Systems offers an out-of-the-box integration with the Nedap !DCloud RFID Solution.

This integration facilitates seamless synchronization between Front Systems and Nedap !DCloud, enhancing inventory accuracy, streamlining stock management, and improving operational efficiency.

Nedap.png


Included Features

  1. Master Data Synchronization
  2. ERP Stock Synchronization
  3. Approved Difference List Processing
  4. Shipment Upload
  5. Shipment Received Synchronization
  6. Shipment Sent (Inter-Branch Transfer) Synchronization
  7. Sales/Returns Synchronization

Prerequisites

RFID Location Setup

For the integration to function correctly, customers must set up the RFID location in the stock settings within the Front Systems portal for each stock that is enabled in !DCloud.

The RFID location typically follows the format: http://nedapretail.com/loc/store-512084.

1. Master Data Synchronization

Description

  • Purpose: Synchronizes product master data from Front Systems to Nedap !DCloud.
  • Frequency: Occurs every 20 minutes.
  • Scope: Targets products in Front Systems that have been modified since the last successful synchronization.

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.

2. ERP Stock Synchronization

Description

  • Purpose: Synchronizes a snapshot of stock levels from Front Systems to 'ERP stock' in Nedap !DCloud.
  • Frequency: Occurs every 40 minutes.
  • Scope: Includes a complete snapshot of current stock levels.

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.

3. Approved Difference List Processing

Description

Purpose: Real-time adjustment of stock levels in Front Systems based on an approved difference list from a stock count in Nedap !DCloud.

 

push-pin.png N.B.

Only retrieves the differences from Nedap !DCloud, not the complete stock count.
For detailed reporting, customers should use !DCloud reports.

 

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.
  • SaveAsStockCount:
        • Default: 0
        • Usage: Set to 1 if the difference list adjustment should be saved as a stock count in Front Systems. Be aware that the stock count report in Front Systems will be incomplete since only differences are included.

4. Shipment Upload

Description

  • Purpose: Synchronizes Front Systems deliveries to !DCloud shipments.
  • Trigger: Occurs in real-time when a new or changed delivery is made in Front Systems.
  • Behavior: Deletes existing shipment in !DCloud and uploads the updated delivery.

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.
  • DCLocation:

5. Shipment Received Synchronization

Description

  • Purpose: Synchronizes receipts of shipments in !DCloud to Front Systems delivery receipts.
  • Trigger: Occurs in real-time upon receipt in !DCloud.

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.
  • ArchiveOnReceipt:
      • Options: true or false
      • Usage: If set to true, the delivery in Front Systems will be archived regardless of whether it is a complete receipt.

6. Shipment Sent (Inter-Branch Transfer) Synchronization

Description

Purpose: Real-time synchronization of shipments sent in !DCloud to Front Systems product transfers between stores.

Integration Details

  • IDCloudToken: The API token for Nedap.
  • FrontApiKey: The API key for Front Systems with company/unlimited scope.
  • DeleteShipmentInNedapAfterSyncToFront:
      • Default: false
      • Usage: Used in special cases only (e.g., specific customer requirements).

7. Sales/Returns Synchronization

Description

  • Purpose: Real-time synchronization of Front Systems sales and returns to Nedap !DCloud (EPCIS events).
  • Functionality: Deactivates RFID alarms for items upon sale or return.
  • Implementation: Occurs via a Keystone service in the POS that pushes sale/return events to !DCloud.

Integration Details

  • IDCloudToken (ServicePass): The API token for Nedap.
  • IDCloudClientID (ServiceKey1): The client ID for Nedap.
  • IDCloudClientSecret (ServiceKey2): The client secret for Nedap.

 

Related articles

Comments

0 comments

Please sign in to leave a comment.