What reporting limitations exist in MerchantSpring?

MerchantSpring provides comprehensive marketplace analytics, but like all reporting platforms, certain limitations exist due to how data is provided by external systems such as Amazon.

Most reporting constraints are related to data availability through marketplace APIs, rather than limitations within MerchantSpring itself.

Understanding these constraints can help users interpret reports more effectively.

---

Common Reporting Limitations

Data Availability From Marketplaces

MerchantSpring retrieves data from official marketplace APIs. If certain datasets are not available through these APIs, they cannot be included in reports.

Examples may include:

• proprietary metrics that Amazon only displays within its internal dashboards

• experimental advertising metrics

• estimated values not exposed through APIs

Reporting Latency

Some datasets are published with delays, particularly:

• financial adjustments

• advertising attribution data

• settlement updates

This can cause short-term differences between reports.

Attribution Models

Advertising metrics rely on attribution models defined by the advertising platform. These models determine how conversions are credited to ads.

Because attribution windows vary, advertising metrics may update over time.

---

Best Practices for Interpreting Reports

To ensure accurate analysis:

• review longer reporting periods when possible
• allow time for financial adjustments to appear
• understand how attribution windows affect advertising metrics

Following these practices helps produce more reliable insights.

---

Notes: 

• Reporting accuracy depends on the data provided by connected marketplaces.
• Financial events and advertising metrics may update after the initial transaction.
• Minor discrepancies during recent reporting periods are normal.

If you have questions about reporting data or need help interpreting results, please contact support@merchantspring.com.au.