06:00 UTC













Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Enter the Azure SQL server host, database, and login details. Catchr verifies the destination before any marketing data is exported.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your AzureSQL table.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about AzureSQL setup, available source data, schedules, table updates, and SQL use cases.
Authorize Amazon Vendor Central with OAuth, select the marketplace you want to report on, save your Azure SQL connection details, and pair both systems in a datastream. Then choose the report fields and Azure SQL table for the job.
Build Azure SQL tables from fields such as ordered revenue, shipped revenue, ordered units, open purchase order units, inventory costs, average vendor lead time, report level, and normalized dates. You can select and rename the columns before writing them.
Sales, traffic, inventory, and net pure product margin reports can use the requested date window, while forecasting returns Amazon's latest forecast snapshot. Available history and recurring frequency depend on the Amazon API and your Catchr plan.
For reports that use a date window, select a valid normalized date field when configuring the job. Catchr deletes and rewrites the scheduled window, helping limit duplicate rows across overlapping loads; forecasting should be treated separately because it returns the latest snapshot.
Use Azure SQL queries or views to compare ordered and shipped revenue, track ordered and unfilled units, monitor sellable, unhealthy, aged, and unsellable inventory costs, or analyze vendor lead time. Report-level fields let you distinguish aggregate results from ASIN-level rows.
Yes. Connect an existing Azure SQL database first. The Catchr job creates and populates the destination table you configure inside that database.
Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.
Our teams is always here to responds to any question you could have about our data connector.