Store Implementation: Products and Orders

The store implementation is responsible for receiving updated products and orders from Talk2Sync, transforming the incoming data, and inserting or updating it in the external application.

The target system can be a legacy ERP, database, or another application. The storage operation may be performed through different integration mechanisms, including:

  • Direct database access such as JDBC or ODBC.
  • APIs such as SOAP or REST.
  • COM interfaces.
  • Filesystem-based integrations.
  • Other mechanisms supported by the target application.

The critical requirement is that the implementation must determine whether the data was actually stored or updated successfully and report the result to Talk2Sync.

Store Implementation Products

When Talk2Sync sends an updated product, the connector must:

  1. Receive the product from Talk2Sync.
  2. Transform the product into the format required by the target system.
  3. Insert the product if it does not exist, or update it if it already exists.
  4. Verify whether the operation succeeded.
  5. Report the result back to Talk2Sync.

If the storage operation fails, the connector must report the error so that Talk2Sync can retry the same insert or update during a subsequent synchronization.

Store Implementation Orders

The order storage process follows the same pattern.

When Talk2Sync sends an updated order, the connector must:

  1. Receive the order from Talk2Sync.
  2. Transform the order into the target system's format.
  3. Insert or update the order.
  4. Verify that the operation completed successfully.
  5. Report the result to Talk2Sync.

If the operation fails, the error must be reported to Talk2Sync so that the update can be retried during a later synchronization.

Why Error Reporting Is Required

The storage result is an essential part of the synchronization transaction.

When the connector reports an error, Talk2Sync knows that the operation was not completed and can attempt to send the same update again during a subsequent synchronization cycle until the storage operation succeeds.

If the connector does not report an error, Talk2Sync assumes that the storage operation succeeded. It will therefore not retry the update later.

In that situation, a subsequent synchronization may interpret the previous values as having changed again and propagate those changes to other connections configured in Talk2Sync.

Important: Always report the actual result of the storage operation. Do not acknowledge a transaction as successful unless the target system has successfully stored or updated the data.

Storage Flow

Next Steps

Last Updated: