FAQ’s

REGYSTRD pulls your order history through API and/or through file upload. Using just an order number and an email, customers can then register their purchases, and then make claims against covered SKUs from those orders. Sellers can have those claims be automatically processed(through 'policies'), or they can manually review them. Approved claims generate fulfillment order requests that can be sent to a 3PL (e.g. Amazon FBA)

With REGYSTRD, your customers can make their own claims, subject to the terms and conditions that you set. You can opt to have those claims automatically processed(by policy) or you can manually review them. Claim review is streamlined because you can see a customer's order, return, refund, and claim history at a glance. And with just a couple of clicks, REGYSTRD can send fulfillment requests to your 3PL. Time is money. and REGYSTRD saves you on both.

SKU mapping is at the heart of REGYSTRD. First, you indicate which of your SKUs is covered by warranty. Then you specify which SKUs can be sued to satisfy a claim. Old SKUs can be mapped to Active SKUs, bundled SKUs can be mapped to their component SKUs, and SKUs can be mapped to part SKUs. Between mapping, terms and conditions, and policies, REGYSTRD will prevent anyone from claiming more than they should.

It depends mainly on the the number of SKUs covered by your warranty, whether or not those SKUs are bundles or have parts, and how many covered SKUs have been replaced by new SKUs. Onboarding for a basic implementation - with no historical, bundle or part mapping - can take as little as 20 minutes.

Yes. And we think you won't find a better solution to get one started than with REGYSTRD. With REGYSTRD, you're in full control, unless you don't want to be, in which case you can set up a low-maintenance auto-mated warranty system. Dip your toes into the world of Warranty Marketing.

Yes. And the only thing you'll have to do differently from a seller starting a new program is to upload your prior registrations. Additionally - though not required - you can upload your claim history.

Yes. All customers may enjoy the first 30 days of REGYSTRD for free. This gives you time to ensure a tight configuration and for you to familiarize yourself with this powerful system.

Yes. Using the Amazon SP-API, REGYSTRD pulls order, return, and refund information. It can also create, send, and cancel fulfillment order requests for Approved customer claims.

So long as they are part of the same Seller Central account, you can use REGYSTRD with any Amazon Marketplace, and as many Amazon Marketplaces as you like.

Yes. REGYSTRD integrates with Mailchimp through the Mailchimp Marketing API. When customers register their orders, they are added to an email list. When customers opt-out of marketing emails in REGYSTRD, they are removed from the Mailchimp email list.

REGYSTRD does not currently integrate with Shopify. If you would like to see this feature, please let us know.

REGYSTRD does not currently integrate with WooCommerce. If you would like to see this feature, please let us know.

REGYSTRD currently only integrates with Amazon FBA. For other 3PLs, REGYSTRD offers the ability to export fulfillment orders (on a per-SKU basis, in csv format) for upload into your preferred service provider.

Waranty Terms and Conditions are the limitations you place on customer claims. For instance, you can specify whether a warranthy is limited or unlimited.

You can set: how long after the date of purchase that a claim can be made; the minimum interval between claims; and the maximum number of claims.

No. Currently, REGYSTRD only supports global terms and conditions. However, you can use our 'policies' feature to ensure that SKUs whose terms and conditions deviate from the norm are forced to be manually reviewed.

Amazon's SP-API allows REGYSTRD to pull order history as far back as January 2016.

After initial onboarding (which pulls your entire order history), REGYSTRD will run daily updates to pull in your most recent orders. If a customer tries to register an order that is not yet in the REGYSTRD database, the record is pulled in on-demand (at the time of registration) to ensure a seamless user experience.

REGYSTRD allows you to create manual orders and/or to upload non-Amazon orders in CSV format. However, this is an add-on feature. Please contact us for more information.

Yes. REGYSTRD has a robust orders explorer, which allows you to filter orders by date, location, SKU, SKU count, and order value...just to name a few.

You can add notes to any order in REGYSTRD, which will help with processing claims. However, you cannot edit orders delivered through API; only orders created from within REGYSTRD are editable.

A Registration is the matching of an order number with a customer email. Registrations can be made by customers (it only takes a couple of minutes) or by you, on behalf of your customer. A customer with at least one registration is called a Registrant.

Upon registration (which only requires an order number and an email) the customer/registrant will receive an email confirmation and promotional code, if you have configured the system to do so. They will also be added to any Mailchimp email list you have integrated with.

No. REGYSTRD uses a 'one registration, one order' paradigm. However, REGYSTRD will show you all of a Registrant's related orders, based on their Amazon Buyer email.*

*due to SP-API limitations, buyer email matching only goes back two years from the date of onboarding

Claims can be initiated by either your customers (registrants) or by you. In either case, one simply selects the replacement SKU(s) and counts and provides shipping instructions. The entire process takes just a couple of minutes.

Policies are rules for the auto-processing of claims. Policies are related to Terms and Conditions, but are distinct. For instance, a policy could be that so long as the total value of a claim is under a certain threshold, it does not need to be manually reviewed. A policy might be that if a user has made a claim within the last year, the order must be manually reviewed. Another possiblity would be to say that once a user has reached a certain number of claims (across any and all orders) that manual review is required.

If the claim satisfies all policies, then a fulfillment order request will be automatically sent. Otherwise, you manually review the claim. You can approve or deny the claim, or move it to an 'under review' status pending additional information. You can also edit a claim, in which case REGYSTRD considers it 'settled' instead of mererly 'approved'.

A Claim is merely a record of what is being replaced, or requested to be replaced. Once approved, you must authorize a Fulfillment to satisfy the claim. Authorizing a Fulfillment sends a fulfillment order request to your 3PL. So, you might have an 'approved' claim that has not been fulfilled, or single approved claim with more than one Fulfillment from different 3PLs.

Currently, REGYSTRD only supports FBA fulfillments through SP-API. However, if you use a different 3PL for some SKUs (e.g. for parts), then you can export those Fulfillments to CSV for upload into your 3PL. REGYSTRD automatically divides a 'mixed' Claim into two Fulfillments: one for FBA, and one for export.

Yes, REGYSTRD is a whitelabel product. You can upload your logo, a favicon, and set text and buttons to brand-compliant colors.

Yes, most all of the customer-facing text (e.g. for registrations, claims, contact form, email templates) is fully customizable.

Yes, REGYSTRD allows you to specify whether or not your customers receive registration and claim confirmation emails. And you have control over their appearanceand content.

Yes, promotional codes are an option. You simply have to enable the feature and either specify a global code (that you have set up in Seller Central) or else upload a list of unique codes. If you want, REGYSTRD will ntofiy you when your code inventory is running low.

Yes, REGYSTRD allows you enable an expedited shipping option.

With REGYSTRD, you can specify whether or not your warranty is 'no questions asked' or whether you'd like to be provided a reason for a claim; you can designate separate system notification and customer service emails; ou can also specify whether or not you recieve system alerts and registration/claim notifications.