Data Scrape to Database

Do you want the system to create unpublished inventory/offers in eBay for manual review, or should it publish the listing automatically after approval?

Hi Jon,

A few details would help us define the scope correctly:

1. Which Amazon marketplace will the links come from, such as Amazon UK, US or another region?

2. Do you already have access to an Amazon-approved product API, or are you expecting a direct scraping solution?

3. Approximately how many products will be imported each day or month?

4. Should the system support products with variations such as size, colour or pack quantity?

5. Which exact user-defined fields and tick boxes do you need?

6. Will there be one system user or several users with separate accounts?

7. Do you want eBay products saved for review first, or published automatically?

8. Which eBay marketplace and seller account type will be used?

9. Should the system also track later changes such as listing status, stock, price or sales?

10. Will product descriptions and images be reused exactly, or edited before being listed?

Looking forward to your reply!

Hi Jon,

A few details would help us define the scope correctly:

1. Which Amazon marketplace will the links come from, such as Amazon UK, US or another region?

2. Do you already have access to an Amazon-approved product API, or are you expecting a direct scraping solution?

3. Approximately how many products will be imported each day or month?

4. Should the system support products with variations such as size, colour or pack quantity?

5. Which exact user-defined fields and tick boxes do you need?

6. Will there be one system user or several users with separate accounts?

7. Do you want eBay products saved for review first, or published automatically?

8. Which eBay marketplace and seller account type will be used?

9. Should the system also track later changes such as listing status, stock, price or sales?

10. Will product descriptions and images be reused exactly, or edited before being listed?

Looking forward to your reply!

- What custom fields would you like available within the database, and should these fields be configurable by you in the future?

- When creating draft listings on eBay or other marketplaces, what information should be automatically populated, and what should remain editable before publishing?

Hey John, should the database status update only when eBay returns a successful draft-listing ID, or should it also stay synchronised if that draft is later edited, published or deleted in eBay? This determines whether we build a one-way confirmation workflow or ongoing two-way synchronisation.

To begin, we would need:

- 2–3 representative Amazon product URLs covering the typical data and image variations.
- Your required database fields, including the tick boxes, free-text fields and Excel export columns.
- Confirmation of the database environment and buyer-controlled eBay developer/API access, plus one example of the intended eBay category and listing structure.

Once these are shared, we can begin immediately.

Hi Jon,
Are you open to proposals for one layer only? Or the proposals must fulfill the two layers?
Thanks

Is the Amazon import intended as a one-time migration, or should new product changes be synchronized automatically?