Someone has offered to build a website that imports product and shopping data from marketplaces in one country and makes it available on another site where customers can log in and place orders. Because of geographic, payment, banking, and phone-number restrictions, customers would use the intermediary rather than buying directly from the original marketplace.
The system would use one main purchasing account, support multiple customer subaccounts, provide an administrative backend, and include a translated customer-facing frontend. It would work similarly to existing proxy-shopping services that let international customers purchase items from marketplaces such as Mercari or Yahoo Auctions.
I am trying to estimate two things: how much a system like this might cost to build, and what a reasonable ongoing maintenance fee would be. I am also concerned about risks involving marketplace terms of service, payment handling, taxes, customs, refunds, fraud, privacy, and cross-border regulations. Are these concerns substantial enough to require legal advice before development begins?
4 Answers
The biggest business question is who carries the risk when something goes wrong. If an order is lost, counterfeit, damaged, rejected by customs, refunded late, or purchased from a suspended marketplace account, customers will likely look to the intermediary. Budget for customer support, dispute handling, insurance where available, security testing, backups, and operational staff in addition to the software build.
There is no reliable flat price without a detailed specification. A basic catalog import is very different from a production system handling accounts, payments, order placement, translation, inventory changes, shipping, refunds, fraud prevention, notifications, and marketplace API or scraping restrictions. Get a written scope and quotes from several experienced development teams. Maintenance should be treated as a continuing engineering budget for hosting, monitoring, security, bug fixes, marketplace changes, and support—not just a small monthly fee.
The legal and compliance side is a major part of the project, even if similar services already exist. You may be operating across multiple jurisdictions and could become responsible for customer funds, personal data, consumer protection, customs, taxes, prohibited goods, chargebacks, and account restrictions. Have qualified lawyers review the business model, marketplace terms, payment flow, and privacy obligations before committing to development.
Make sure the proposed developer explains exactly how the data and orders will be obtained. Unauthorized scraping, automated purchasing, or using a shared account may violate marketplace rules and can stop working without warning. Official APIs and commercial agreements are much safer when available, but they can significantly increase the cost. A small proof of concept should come only after confirming that the intended workflow is permitted.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads