This document provides detailed guidelines for how data is entered into DCKAP Integrator — either via API payloads from connected systems or via manual configuration in the portal — and defines the validation rules applied to ensure data integrity throughout the integration lifecycle.
2. Data Entry Channels
Channel
Description
Primary Users
Source System API
Automated payloads pushed by eCommerce/ERP systems
Connected Systems
Webhook Events
Real-time event payloads (e.g., order.created)
Connected Systems
Portal — Field Mapping
Manual field configuration by customer admins
Customer Admins
Portal — Business Rules
Manual logic configuration for transformations
Customer Admins
Bulk Upload (CSV/JSON)
Batch record uploads for initial data loads
Customer Admins
API (DCKAP API)
Programmatic record injection via DCKAP REST API
Developer Users
3. Validation Rule Categories
3.1 Format Checks
Field Type
Format Rule
Example
Date
ISO 8601 — YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ
2026-04-27
Currency Amount
Decimal with 2 decimal places, no currency symbol
1250.99
Email Address
RFC 5322 email format
user@example.com
Phone Number
E.164 international format
+12025551234
SKU / Product Code
Alphanumeric, max 50 chars, no special chars except -_
SKU-PROD-001
Postal / Zip Code
Format varies by country; validated against country field
EC1A 1BB
3.2 Range Checks
Field
Min
Max
Action on Breach
Order Quantity
1
99,999
Reject with error
Unit Price
0.00
999,999.99
Reject with error
Discount %
0
100
Reject with error
Tax Rate %
0
100
Reject with error
Sync Interval (mins)
1
1440
Default to 60 mins
3.3 Consistency Checks
Order total must equal sum of line item totals ± rounding tolerance of ±0.01.
Shipment must reference a valid order ID present in the destination system.
Customer ID on an order must exist in the customer master if reference validation is enabled.
Start date must be before end date for any date-range fields (e.g., promotions).
3.4 Portal Configuration Validation
Field mapping rules are validated for circular references before saving.
Business logic expressions are syntax-checked in real time in the rule editor.
Connector credentials are tested against the live API before the connection is saved.
