PostgreSQL eCommerce Database Developer for Payments and Refunds
The client needs a PostgreSQL eCommerce database developer to design a back end for payments, refunds and full transaction history. The brief covers the schema, DDL scripts, an ER diagram and seed data for smoke tests.
- Open ยท checked 12 Nov 2026
- ๐จ๐ฆ Canada (budget currency)
- Sql
Is the budget fair? The CA$250โ750 CAD budget looks workable if the work stays on the payments, refunds and transaction module. It looks tight if the client later adds the products and orders parts that the brief mentions as wider needs.
What the client needs
- Design a PostgreSQL schema for payments, refunds and transaction history.
- Write DDL scripts that run on a clean PostgreSQL instance.
- Produce an ER diagram as a PDF or PNG.
- Add seed data and short notes on non-obvious design choices.
Skills the client asked for: SQL, eCommerce, MySQL, Database Administration, PostgreSQL, Database Programming, Database Development, Database Design.
Where to aim your bid
The sweet spot sits about 40% of the way up the client's range, the same rule AutoBidPilot uses for its own price suggestions. Go higher when the scope is large or unclear; go lower only when you can show close, finished work. Check what you keep after fees with the bid price calculator.
What the project involves
The client is launching a new PostgreSQL back-end and wants it designed from scratch to power an ecommerce workflow. It must store products, orders and payments, with the first release focused on payments, refunds and full transaction history.
Deliverables
- A well-structured schema with tables, relationships, constraints and indexes for reliable payment data
- Clear DDL scripts that run on a clean PostgreSQL instance
- An ER diagram as PDF or PNG
- Simple seed data for smoke tests after deployment
- Brief documentation of non-obvious design choices and the connection string format
Acceptance
The client provides server access. Scripts and docs must run without modification on PostgreSQL 15 or later. The job is done once the migration runs cleanly and the client's test suite confirms inserts, updates and rollbacks.
How to win this project
- Ask for the payment states and refund rules before drafting the schema, since they drive most of the constraints.
- Show a short sample of DDL with constraints and indexes, so the client can judge how you handle payment data.
- Plan the first release around payments only, and name what you will leave for a later module.
Questions to ask the client
A specific question in your first message shows you read the brief. Pick one or two:
- Which payment flows and currencies must the schema support in the first release?
- Can one payment have several partial refunds, and how should the history show them?
- Will you run the scripts on the client's instance, or hand over files only?
Common questions
How much does a PostgreSQL ecommerce database developer cost?
The posted budget is CA$250โ750 CAD for this project. Check whether it covers the ER diagram, documentation and seed data as well as the schema and scripts.
What does the database scope include?
The brief asks for tables, relationships, constraints and indexes for payment data, DDL scripts for a clean instance, an ER diagram and seed data. Confirm each item before you bid.
Is this project still open?
We checked this project on 10 November 2026. Projects get awarded, so apply soon; we take a brief down when it closes.
This page is our own summary of a project posted online, written to help you decide and to write a better bid. Projects get awarded or closed, so apply soon; we take a brief down when it closes. No job or income is guaranteed.