✨New Features

Stord — New Connector

What's new — Daton now supports a new Stord connector that retrieves facility-level inventory data directly from Stord's API into BigQuery. Currently supports the Facility Inventory table.

How it works — The connector accesses the Stord API endpoint (/inventory/reports/facilities) to provide per-SKU, per-warehouse inventory balances including allocated, available, incoming, and total on-hand quantities across your fulfillment network.

Why this matters — Operations and supply chain teams can now track warehouse-level inventory positions in real time, enabling accurate stock forecasting, multi-location inventory planning, and fulfillment network optimization.

Do you need to do anything? — If you use Stord for inventory management, create new Stord integration from Daton. Provide your Stord API credentials and organization/network IDs.

🚀Enhancements
 

Daton Alerts — Immediate Alert

What we improved — Enhanced the monitoring alerts system with "Immediate Alert" capability. For integrations with run frequency of 6+ hours, you can now enable immediate alerts on both action-required failures and consecutive errors—no more waiting for the 3-failure threshold (which can mean 18–72 hour delays). Click here to learn more about Daton Alerts.

How it works — System automatically detects your integration's sync frequency and determines the alert mode. For infrequent syncs (6+ hours), immediate alerts are sent on first failure so you catch issues faster. For more frequent syncs, alerts are sent after 3 consecutive failures. Retries follow your configured schedule; only the alert timing changes. Recovery notifications are sent if a retry succeeds.

Why this matters — Critical data pipelines on daily or weekly schedules are no longer blind for hours. You catch issues immediately and can respond faster to data issues.

Do you need to do anything? — Enable Immediate Alert in your integration settings if your sync runs every 6+ hours and you want real-time failure notifications.

Walmart WFS Inventory — New Inbound and Out-of-Stock Fields

What we improved — Added two new fields to the Walmart WFS Inventory connector: InboundUnits and OutOfStockDate, providing deeper visibility into inventory status and incoming shipments.

How it works — The connector now pulls data from Walmart's WFS Inventory Details API endpoint, exposing inbound unit counts and estimated out-of-stock dates alongside existing inventory metrics.

Why this matters — You can now track pending inbound inventory and forecast stockouts directly from your warehouse data, enabling proactive inventory planning and reducing stockouts.

Do you need to do anything? — The new fields are available to add to your Walmart WFS integration. Select them in your connector configuration to start receiving the data.

Recharge — Events Table Stability Resolution

What we improved — Resolved recurring 422 errors in the Recharge Events table that were preventing data ingestion, ensuring stable access to Recharge events for subscription analytics.

How it works — The Recharge Events API is limited to 7 days of historical data, which was causing 422 errors when the system attempted to retrieve older records. We added a history limiter to the connector's request logic to respect this API constraint, ensuring requests stay within the 7-day window and prevent the 422 errors.

Why this matters — Your Recharge Events data now flows reliably into your warehouse without interruptions, providing complete subscription lifecycle tracking.

Do you need to do anything? — No action required. The fix has been deployed to all Recharge integrations.

BigCommerce — Shipments Table Data Loading Resolution

What we improved — Resolved a long-running job issue that was preventing data from loading into the BigCommerce shipments table.

How it works — Fixed platform-level job handling to ensure successful data ingestion from BigCommerce APIs.

Why this matters — Shipments data now flows reliably for BigCommerce integrations, ensuring your warehouse has current shipping information.

Do you need to do anything? — No action required.

Amazon Selling Partner — Rate Limit Handling for Child ASIN Reports

What we improved — Updated rate limit handling for the GET_SALES_AND_TRAFFIC_REPORT endpoint used by the Amazon Seller connector when fetching Child ASIN data.

How it works — The connector now implements dedicated rate limit handling to prevent timeouts and errors when processing large volumes of Child ASIN report data.

Why this matters — Your Amazon Seller report syncs are now more resilient, reducing failures and ensuring consistent data availability for your Child ASIN metrics.

Do you need to do anything? — No action required. The improvement has been applied to all Amazon Seller integrations.

Shopify — Refunds Table Schema Update for Multi-Value Fields

What we improved — Fixed schema definition for the Shopify Refunds table to correctly handle multi-value fields in BigQuery. The amount_rc field under refunds transactions can now properly store array values when transactions involve multiple payment splits.

How it works — Updated the field mode from NULLABLE to REPEATED in the BigQuery schema, allowing the connector to load transactions with multiple refund amounts without parsing errors.

Why this matters — Shopify Orders and Refunds data now syncs reliably for all transaction types, including complex partial refunds with multiple payment methods or splits.

Do you need to do anything? —  The fix has been deployed. You can modify your existing integrations.

Stay AI — BigQuery JSON Parsing Error for Subscriptions Table

What we improved — Resolved JSON parsing errors in the Subscriptions table that were preventing data from loading into BigQuery.

How it works — Enabled string parsing at the EST level to correctly handle JSON field formats in Subscriptions data, ensuring all records successfully load into your warehouse.

Why this matters — Your Subscriptions data now syncs reliably without JSON parsing failures, maintaining data integrity and completeness.

Do you need to do anything? — No action required. The fix has been deployed and data is now loading successfully.

Fulfil  — API Error Handling and Reliability Improvements

What we improved — Enhanced the Fulfil connector's API error handling and request processing to resolve 400 errors that were preventing data syncs for sources with specific API request patterns.

How it works — Updated the connector's request validation and error recovery logic to handle edge cases in Fulfil API responses and improve overall source reliability.

Why this matters — Fulfil sources now sync more reliably with improved error handling and recovery, reducing sync interruptions.

Do you need to do anything? — No action required. The improvement has been deployed to all Fulfil integrations.

AppLovin — Schema Standardization

What we improved — Standardized the AppLovin connector schema across both Daton and Pulse platforms by removing the hour field from reporting tables, resolving data processing performance issues.

How it works — The hour dimension has been removed from the AppLovin connector's source code. This significantly reduces query complexity and execution time, allowing reports to complete reliably within system limits.

Why this matters — Removing hourly granularity reduces computational overhead by approximately 24x, enabling AppLovin integrations with high-dimensional data (many campaigns, countries, and ad types) to sync without timeouts. Data is still available at daily granularity across all dimensions.

Do you need to do anything? — No action required. If you currently use the hour field in your AppLovin dashboards or models, update your queries to use daily data instead.

TikTok Shop — Hibernation State Size Limit Fix

What we improved — Resolved hibernationSourceLogState size cannot exceed 10 MB errors affecting high-volume table syncs (e.g., TikTok Shop Orders table). Implemented permanent fix by optimizing partition sizing strategy.

How it works — Updated the platform's default partitionSize configuration to reduce the volume of state information stored during processing for large datasets.

Why this matters — High-volume tables can now sync reliably without hitting state size limits, enabling data ingestion for tables with large row volumes or complex data structures.

Do you need to do anything? — No action required. The fix applies automatically to all new integrations and has been applied to existing affected integrations.

🛠️Fixes

Amazon Selling Partner — Add Columns Utility Now Functioning

What was the issue — The Add Columns utility in the Amazon Seller connector configuration was not functioning properly. When users added new columns to their tables through the utility, the columns were marked as updated but the configuration changes were not being persisted to the data pipeline.

What we fixed — Corrected the utility's backend logic to properly save column configuration changes, allowing newly added columns to load data correctly into the warehouse.

Why this matters — You can now use the Add Columns utility to expand your Amazon Seller tables with additional fields without encountering configuration errors.

Do you need to do anything? — No action required. If you previously had issues adding columns, try again now — the utility is fully functional.
 

Amazon Selling Partner — Dedicated Rate Limit Handling for Child ASIN Reports

What was the issue — The GET_SALES_AND_TRAFFIC_REPORT endpoint in the Amazon Seller connector was experiencing rate limit errors when fetching Child ASIN-level data, particularly for large product catalogs, causing syncs to stall.

What we fixed — Implemented dedicated rate limit handling logic for this specific endpoint, including intelligent retry logic and request batching to stay within Amazon's rate limits.

Why this matters — Your Amazon Seller Child ASIN reports now sync reliably without rate limit failures, ensuring your detailed product performance data is always current.

Do you need to do anything? — No action required. The fix has been deployed to all Amazon Seller integrations.
 

MNTN — Connector Endpoint Issue Resolution

What was the issue — The MNTN connector was failing to sync data due to an API endpoint configuration issue that was preventing successful authentication and data retrieval.

What we fixed — Corrected the connector's API endpoint configuration to properly communicate with MNTN's servers, restoring data ingestion.

Why this matters — If you use MNTN for advertising performance tracking, your data syncs are now restored and running reliably.

Do you need to do anything? — No action required. The fix has been deployed to all MNTN integrations.
 

Amazon Selling Partner — Excessive Data Processing and Duplicate Date Range Issue

What was the issue — The Amazon Selling Partner connector was processing excessive data volume with duplicate date ranges during syncs, leading to inefficient pipeline usage and potential data inconsistencies.

What we fixed — Corrected the date range calculation logic to eliminate duplicate overlaps and optimize the data processing pipeline for efficient incremental syncs.

Why this matters — Amazon Seller data syncs are now more efficient and accurate, with correct date range handling preventing duplicates in your warehouse.

Do you need to do anything? — No action required. The fix has been deployed and applies to all Amazon Selling Partner integrations.
 

Amazon Ads — Individual Table Selection Issue Fix

What was the issue — Users were unable to select individual tables during Amazon Ads integration setup. Only the "Select All Tables" option was functional, forcing users to ingest all tables then manually deselect unwanted ones.

What we fixed — Re-enabled individual table selection in the integration setup UI, allowing users to customize which tables they want to ingest.

Why this matters — You now have full control over table selection during setup, reducing initial data volume and simplifying configuration.

Do you need to do anything? — No action required. The fix applies to all new Amazon Ads integrations.

Amazon Sponsored Products/Brands — JSON Parsing Error Fix

What was the issue — Multiple Amazon Sponsored Products and Sponsored Brands tables were failing with a Jackson JSON parsing error (Cannot invoke JsonNode.asText()), affecting reports and creative-level data across multiple accounts.

What we fixed — Corrected the JSON field parsing logic in the Amazon connector to properly handle all field data types returned by Amazon's APIs.

Why this matters — Amazon Sponsored Products and Sponsored Brands syncs now run reliably across all report types and accounts.

Do you need to do anything? — No action required. The fix has been deployed to all Amazon Sponsored Ads connectors.