Claimlane
Claimlane is a warranty, returns and claims management platform that connects retailers, brands and suppliers around product complaints. With Weld you can sync your Claimlane data into your data warehouse to report on claim volumes, refunds, faulty products and handling workload, and combine it with your ecommerce, product and finance data.
Features
| Feature name | Supported | |
|---|---|---|
| Column Hashing | True | Column level |
| Blocking | True | Column level |
| Incremental | True | |
| Custom data | False | |
| History | True | |
| ReSync | True | Table level |
| Templates | False |
Data Schema
Setup Guide - ELT
Prerequisites
You need a Claimlane API key. Both company keys and supplier keys work, and the key decides which retailers and suppliers Weld can see. Weld only reads from Claimlane, it never writes back.
Step 1 - Get your Claimlane API key
- Sign in to Claimlane with an account that can manage your organization's integrations.
- Generate an API key for Weld. If you can't find where to create one, ask your Claimlane administrator or your Claimlane contact to issue a key for you.
- Copy the key.
Step 2 - Create the connection
- In the Weld app, navigate to Connections and click + New Connection.
- Search for Claimlane and select it.
- Enter the destination schema name of your choice. This name is used to identify the connection in future syncs.
- Paste your API key.
- Click Connect to validate the key and establish the connection.
Step 3 - Choose organizations
Most Claimlane data belongs to a retailer or a supplier organization. Under Organization settings, the Organizations list shows every retailer and supplier your API key can see, labelled with its type (for example Acme - supplier).
- Select the organizations you want to sync.
- Leave the list empty to sync every organization the key can see, including ones added later.
Step 4 - Data To Sync
Select the tables you wish to include in the sync. You can view the schema, remove columns or hash sensitive information.
Organizations
retailersupplier, which brings alongsupplier_brandandsupplier_brand_product_identification
B2B claims
b2b_ticket, claims raised against a supplier, which brings alongb2b_ticket_productand its subtablesb2b_ticket_product_id,b2b_ticket_product_tag,b2b_ticket_product_identification,b2b_ticket_product_brand_tag,b2b_ticket_product_internal_supplier_statusandb2b_ticket_product_data_source_tag
B2C claims
b2c_ticket, consumer claims, which brings alongb2c_ticket_shipping_line,b2c_ticket_package_number,b2c_ticket_data_source_tagandb2c_ticket_product, with its subtablesb2c_ticket_product_property,b2c_ticket_product_refund,b2c_ticket_product_partandb2c_ticket_product_data_source_tag
Raw data exports
One table per Claimlane raw data export, with the columns set up in your own Claimlane account:
raw_b2b_product_dataraw_b2b_workload_dataraw_b2c_agent_dataraw_b2c_product_dataraw_b2c_product_part_dataraw_b2c_workload_data
Every raw data row carries organization_id and organization_type, and is identified by a row_hash column. When a row changes in Claimlane, the new version arrives as a new row alongside the earlier one.
b2b_ticket needs at least one supplier in reach. If your API key only sees
retailers, or your organization selection names no supplier, b2b_ticket
can't be synced, but every other table can.
Step 5 - Configure sync
- Select how often you would like the data to sync.
- Provide a unique destination table name.
Weld will take over from here and commence syncing data from your Claimlane account.
Raw data exports start from the beginning of the year three years before your first sync. Records deleted in Claimlane are not removed from tables that have already synced; run a ReSync of a table if you need it to match Claimlane exactly.