Returns Data Feed

outline if your business runs its reporting out of a data warehouse or bi tool rather than the refundid dashboard, refundid can deliver returns data straight into your own cloud storage as a flat file your existing pipelines pick it up from there no one has to export a report by hand, and no one needs a refundid login to build a dashboard this is separate from the reports docid\ hu6vfhyjb78bmj2f1pebb you can build and schedule in the merchant portal, and separate from the refundid apis docid 8ryixthxwvndzjnsjstpl it suits teams who already have a warehouse and simply want the data landing in it what gets delivered a csv with one row per returned line item, so the file can be loaded straight into a table without unnesting anything each row carries both the return level and item level detail return return id, rma reference, order number, return status, resolution and customer email refund breakdown subtotal, return fee, customer shipping cost and total, each with its currency shipping carrier, tracking number, tracking status and the date of the last tracking update item sku, barcode, product and variant references, title, variant, quantity and unit price tax tax amount, currency and whether tax was included in the price return reason the reason, any follow up reason, and the notes or answers the customer gave outcome the per item resolution, whether it was restocked, and any processing notes image url for the returned item returns with no line items still produce a row, so a return never silently disappears from the feed where it's delivered files are written to a cloud storage bucket you own and control for example amazon s3 using credentials you provide two copies are written on every delivery a rolling latest file at a fixed path, for pipelines that simply read the most recent file a timestamped archive copy , so you keep a complete history and can replay or audit any delivery when it's delivered the feed is event driven a file is produced as returns move through their lifecycle, so data lands within moments of the event rather than waiting for an overnight batch if you'd prefer scheduled batches instead, that can be configured getting connected to get set up we need the bucket name and region access credentials scoped to write to that bucket the paths you'd like the latest and archive files written to which return events you'd like a file produced for reach out to your account manager or merchant\@refundid com mailto\ merchant\@refundid com to get set up