🛠️Fixes

Amazon selling Partner; ListFinancialEvents - MaxResultsPerPage Error
 

What was the issue

Job failed with the error: “MaxResultsPerPage must be an integer between 1 and 100.” In this case, the parameter unexpectedly became 0, which Amazon rejects as invalid.

What we fixed

We implemented a safeguard that automatically resets MaxResultsPerPage to a minimum of 1 if it ever drops below the valid range. This ensures the request always complies with Amazon’s allowed values.

Why this Matters

Without the safeguard, future API calls might fail if the value becomes 0 again.
With the fix in place, this error will not recur, and API jobs will continue to run reliably.

Do you need to do anything?

No action needed from your side.
Everything is handled in the system.

Missing Data in ShipBob Invoice Table

What was the issue
Pagination wasn’t handled well, resulting in some invoice data not being retrieved.

What we fixed
We increased the page size to 1000 and implemented proper pagination so all pages are fetched. This update has been applied and verified across all active ShipBob integrations.

Why this matters
You’ll now receive the full invoice dataset, with no missing records.

Do you need to do anything?
No action needed

Amazon SP-API – “Exceeded Time for Response” Error

What was the issue?

Some Amazon SP-API calls failed with the error “Exceeded time for response”.
This happens when Amazon takes too long to respond, and the request exceeds the allowed timeout window.

Common causes include:
Large response payloads
High latency on Amazon’s API servers
Client-side timeout limits
Network delays

What we fixed

We’ve optimized our Amazon API handling by improving retry mechanisms to automatically re-attempt requests when Amazon responds slowly.

Why this matters

These improvements reduce the risk of failures caused by temporary Amazon latency and ensure more stable data ingestion.

Do you need to do anything?

No action required.
However, note that Amazon fully controls API response timing; if Amazon repeatedly exceeds the timeout even after retries, the error may still occur and cannot be eliminated entirely.

Missing data in TikTok Shop's Orders & Order Statement Transactions 

What was the issue?

Some customers experienced missing records in TikTok Shop’s Orders and Order Statement Transactions tables. This occurred because the TikTok Orders API occasionally returned incomplete or inconsistent responses—for example, showing a total_count of 86 orders but returning no actual order records and an empty next_page_token.

This inconsistency resulted in Daton skipping data during ingestion.

What we fixed

We added enhanced validation logic in the TikTok Shop connector to ensure no data is skipped when the API response is inconsistent.
The updated logic now:

• Validates whether the number of returned records matches the total_count
• Retries or flags the API call when the response is incomplete
• Performs strict checks before moving to the next page or date range

This ensures accurate and complete ingestion even when the API behaves unexpectedly.

Why this matters

• Prevents missing orders and transaction records
• Ensures reliable reporting, reconciliation, and financial accuracy

Do you need to do anything?

• For ongoing syncs: No action is required. The improved logic is already live.
• For existing discrepancies:
  If you notice historical gaps in the Orders or Order Statement Transactions tables, you may choose to reload the affected tables or contact Daton Support to request a rollback.

🚀Enhancements

Optional Periodic Attribution for Amazon Selling Partner - FlatFileV2SettlementReport

What we improved

We introduced optional Periodic Attribution for FlatFileV2SettlementReport to handle cases where Amazon provides delayed or updated settlement data for older periods (sometimes up to 120 days).

How it works

Daton can now re-request settlement data for a configurable lookback window (up to 90 days).
The re-fetch runs on a defined frequency.

Sample configuration:
Days: 90
Frequency: 14
AttributionEnabled: true

This feature is off by default and only enabled for users who request it.

Why this matters

Captures late or regenerated settlement data published by Amazon. Prevents missing values or gaps caused by Amazon’s delayed settlement updates. Gives clients more control over how far back Daton should reprocess.

Do you need to do anything?

By default, attribution is not enabled automatically.

If you want this feature, just share your preferred:
Lookback Days (up to 90)
Frequency (how often to run the lookback)

We’ll enable it for your integration. Read more here
 

New Table: MarketBasketAnalysisReportMonthly (Amazon Selling Partner)

What we improved

We added support for a new Amazon Selling Partner API - MarketBasketAnalysisReportMonthly table - providing insights into products frequently purchased together at checkout.

How it works

The report includes key co-purchase metrics such as:

• purchasedWithAsin (items bought together)
• purchasedWithRank (ranking by frequency)
• combinationPct (percentage of orders containing the combination)

It helps identify strong product pairings for bundling and cross-sell optimization.

Why this matters

Provides deeper insights into customer buying behavior. Enables data-driven decisions for bundling, ads, and promotions. Supports all Amazon marketplaces. Up to 1 year of historical data available

Do you need to do anything?

For Existing Integrations: Edit your Amazon Selling Partner integration and add MarketBasketAnalysisReportMonthly. Data will begin populating automatically going forward.

For New Integrations: Include this table during integration setup.

✨New Features

Awin Connector Launch

What’s new

We launched the Awin connector. It now brings Awin’s affiliate data directly into your warehouse.

How it works

The connector pulls transactions, commissions, clicks, and publisher details through Awin’s APIs and loads them straight into Daton.

Why this matters

You get clear, timely insight into affiliate performance without manual work or scripts.

What you need to do

Add the Awin connector in Daton, enter your credentials, and start syncing. Read more here

Amazon Sponsored Products & Sponsored Display

Intraday Window for Improved Data Freshness

We have expanded our intraday refresh capability for Amazon Ads connectors.

What’s new

Daton previously refreshed only the current day’s (T) data multiple times throughout the day. With the new Intraday Window, Daton can now refresh data for the last 7 days (T to T-7) more frequently.

How it works

When the Intraday Window is configured:

• Daton automatically fetches updated Amazon Ads data every 2–3 hours.
• Refreshes apply to all days within the selected window, not just the current day.
• This ensures more frequent updates for recent historical data, which Amazon often modifies.

Why this matters

• Significantly reduces discrepancies between Amazon Ads Console and your warehouse.
• Ensures higher data accuracy for reporting and decision-making.
• Captures late or retroactive updates from Amazon that a once-a-day refresh would otherwise miss.

What you need to do

If you're already using intraday refresh, please note that your integration will continue to refresh only the current day’s data (T) unless you request an update.

To enable the new Intraday Window (1–7 days) and start refreshing historical days (T to T-7) throughout the day, please contact the Support Team.