Moving Marketplace Website w/ Bubble
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
1. Project Overview
Build a production-ready moving-services marketplace in Bubble with public pages, AI inventory recognition, automated pricing, customer offers, moving-date auctions, referral tokens, reservations, customer dashboards, email/SMS, administration, and a white-label partner program. Use shared databases and workflows for regular and partner customers.
2. Pages and Responsive Design
Include homepage, About Us, Contact Us, How It Works, pricing explanation, moving-company network, guarantees, FAQs, signup entry, passwordless login, Terms & Conditions, and Privacy Policy. Build moving details, inventory review, offer submission, auction entry, leaderboard, token/referral pages, customer dashboards, booking confirmations, admin screens, partner landing pages, and a secure partner portal.
All customer/admin features must work on desktop, tablet, and smartphones, including uploads, editing, bidding, reporting, and management screens.
3. Inventory and AI
Import a supplied catalog of approximately 400 household items with cubic-foot values. Provide no-code admin controls for descriptions, categories, volumes, and active status.
Customers select items/quantities, upload multiple photos, or provide written inventory lists. Integrate approved AI to identify items/quantities and map them to the catalog. Allow review, correction, additions/removals, and duplicate resolution before confirmation. Flag uncertain/unmatched results; do not assign arbitrary values. Prevent double-counting across submission methods.
Total volume = sum of confirmed item quantity multiplied by assigned cubic feet. Preserve uploads, confirmed inventory, quantities, and calculation inputs.
4. Routing, Pricing, and Offers
Collect date and pickup/delivery addresses. Calculate pickup-to-delivery-to-pickup routing and store round-trip miles and drive time. Maintain separate admin-editable marketplace and traditional moving-company rates.
Each price = total cubic feet multiplied by its volume rate, plus round-trip miles multiplied by its mileage rate. Display the traditional estimate first. Keep acceptance thresholds, fulfillment costs, and margins confidential. Preserve issued pricing inputs and agreed amounts when settings change.
Evaluate customer offers on the backend. Accepted offers proceed to booking and cannot be lowered or resubmitted for the unchanged request. Rejected customers may repeatedly increase their offer or explore the auction. Exploration reveals the guaranteed price and offers direct booking or official auction entry; exploration alone does not enroll them.
Require a rejected offer before auction entry. Starting bid = highest rejected offer. Every move qualifies regardless of size, volume, distance, cost, profitability, or rejected amount. No additional minimum auction bid.
5. Customer Access
Allow moving details, pricing, and offers without registration/login. Generate a unique customer ID when the process starts. Collect email and phone at booking commitment or official auction entry without initial password or verification requirements.
Returning customers verify either email or phone with a secure single-use code. Include expiration, resend, failed-attempt protection, logout, and protected sessions. Restore saved records across visits/devices. Do not expose or merge existing records solely because entered contact information matches.
6. Date Availability and Price Protection
Provide an admin calendar to block/unblock dates. Dates are available by default; bookings do not automatically reduce availability. Save availability when the customer selects a date. Later blocking must not invalidate that customer's saved selection; do not recheck it during offers, auctions, or confirmation.
Check voluntarily selected replacement dates when selected. Date-only changes preserve accepted, guaranteed, or winning prices. Recalculate when inventory/address changes affect volume or distance.
7. Auctions and Dashboard
One shared auction per moving date. Defaults: open 14 days before moving day, run 48 hours, close 12 days before moving day. Provide admin-editable schedules and synchronized backend timestamps/countdowns.
Support Upcoming, Live, and Completed states. Allow tokens before/during auctions and bid increases without decreases.
Auction Score = (Current Bid / Customer's Guaranteed Price x 100) + Approved Tokens.
Each approved token adds one percentage point. Automatically update scores/rankings. Show date, status, countdown, bid, guaranteed price, tokens, score, ranking, participation information, results, and booking actions. Freeze final bids/scores/tokens at close.
8. Winners and Reservations
Highest score wins; equal scores use higher dollar bid. Exact score/bid ties require manual admin resolution before announcing a winner. Initial confirmation window: 24 hours; reminder: eight hours. Both are admin-editable.
Expire unconfirmed opportunities and offer them sequentially to the next eligible customer at their own final bid, with a fresh window. Prevent duplicate winning reservations. Record no confirmed winner if exhausted. Auctions remain valid with one real customer; non-winners retain guaranteed-price booking.
Use one reservation system for accepted offers, guaranteed prices, winners, and replacement winners. Apply equal operational priority across booking methods.
9. Referral Tokens and Internal Profiles
Build Earn Tokens with own-post submissions, friends/family invitations, prepared promotional content, and personalized referral links. Friends/family submit without accounts. Associate every submission with the correct customer/auction.
Show Pending, Approved, and Rejected statuses. Admin manually reviews posts. Approval awards one token once and updates scores/rankings. Block duplicate normalized URLs/awards, preserve review history, stop submissions at closing, and prevent late approvals from changing results.
Provide reusable platform-controlled promotional profiles with unique IDs, active status, private notes, and independent per-auction bids, guaranteed-price references, tokens, scores, and status. Allow creation, editing, duplication, activation/deactivation, and assignment/removal. Preserve history, clearly label customer-visible profiles as platform-controlled, and exclude them from customer booking awards.
10. White-Label Partners and Discounts
Use one reusable landing template within the same Bubble app for unlimited partners with dedicated URL paths. Support configurable partner branding, contact fields, and descriptions.
Preserve partner branding/attribution through inventory, pricing, offers, auctions, tokens, dashboards, booking, and returning access. Regular customers retain the standard presentation. Reuse the same catalog, AI, routing, pricing, auction, and reservation systems.
Recognize active partner URLs automatically or validate unique promotional codes, including codes entered on the regular site. Recognized visitors need no code. Both discount stages use the original traditional price: initial 15% reduction plus another 15 percentage points, totaling 30%. Do not compound or apply twice; enforce confidential minimum pricing. Preserve the applicable booking price without another discount. No partner scoring bonuses.
11. Partner Administration and Portal
Provide no-code management of partner records, branding, contacts, descriptions, unique slugs/codes, active status, authorized portal email, access, and statistics visibility.
Track visits, attributed quote requests, and confirmed bookings separately. Count visits, not unique visitors; avoid duplicate quote/booking counts.
Build a separate password-authenticated partner portal in the same app. Partners see only their own branding, landing URL, and all-time visits when enabled. Access and statistics switches are independent. Enforce privacy rules preventing access to customers, inventory, quotes, bookings, auctions, revenue, conversions, other partners, or admin controls.
12. Notifications and Payments
Integrate client-controlled email/SMS for upcoming auctions, starts/results, confirmation reminders, replacement opportunities, and booking confirmations. Provide editable templates, schedules, switches, delivery records, and duplicate prevention. Private links require authorized sessions or passwordless verification.
No website payments, deposits, checkout, payment forms, or payment links. Payment occurs outside the site after completion, before movers leave, through an authorized representative using Venmo, Zelle, or credit card with a 5% fee.
13. Administration, Ownership, and Delivery
Provide catalog, pricing, calendar, auction, referral, booking, mover-assignment, partner, reporting, and export controls. Assignment is manual; customers see assigned provider/contact information while internal notes/history stay private. No mover-facing auction, automated payouts, or automatic assignment/change messages.
All website copy must be editable through the admin backend without code.
Build in client-controlled accounts with individual, restricted, revocable developer access. Obtain approval before adding plugins, extensions, APIs, or other dependencies; disclose costs. Required accounts/licenses must remain client-controlled. Maintain a dependency/access inventory and document databases, workflows, and integrations. Deliver external source code to a client-controlled private repository.
Demonstrate working features; test calculations, auctions, reassignment, duplicates, privacy, notifications, date preservation, partner attribution, and mobile operation. Provide documentation/training and correct agreed-scope audit findings before final acceptance.
Confirm complete regular/white-label scope, development price, timeline, integrations, ongoing costs, and any exclusions or clarification requirements.
Build a production-ready moving-services marketplace in Bubble with public pages, AI inventory recognition, automated pricing, customer offers, moving-date auctions, referral tokens, reservations, customer dashboards, email/SMS, administration, and a white-label partner program. Use shared databases and workflows for regular and partner customers.
2. Pages and Responsive Design
Include homepage, About Us, Contact Us, How It Works, pricing explanation, moving-company network, guarantees, FAQs, signup entry, passwordless login, Terms & Conditions, and Privacy Policy. Build moving details, inventory review, offer submission, auction entry, leaderboard, token/referral pages, customer dashboards, booking confirmations, admin screens, partner landing pages, and a secure partner portal.
All customer/admin features must work on desktop, tablet, and smartphones, including uploads, editing, bidding, reporting, and management screens.
3. Inventory and AI
Import a supplied catalog of approximately 400 household items with cubic-foot values. Provide no-code admin controls for descriptions, categories, volumes, and active status.
Customers select items/quantities, upload multiple photos, or provide written inventory lists. Integrate approved AI to identify items/quantities and map them to the catalog. Allow review, correction, additions/removals, and duplicate resolution before confirmation. Flag uncertain/unmatched results; do not assign arbitrary values. Prevent double-counting across submission methods.
Total volume = sum of confirmed item quantity multiplied by assigned cubic feet. Preserve uploads, confirmed inventory, quantities, and calculation inputs.
4. Routing, Pricing, and Offers
Collect date and pickup/delivery addresses. Calculate pickup-to-delivery-to-pickup routing and store round-trip miles and drive time. Maintain separate admin-editable marketplace and traditional moving-company rates.
Each price = total cubic feet multiplied by its volume rate, plus round-trip miles multiplied by its mileage rate. Display the traditional estimate first. Keep acceptance thresholds, fulfillment costs, and margins confidential. Preserve issued pricing inputs and agreed amounts when settings change.
Evaluate customer offers on the backend. Accepted offers proceed to booking and cannot be lowered or resubmitted for the unchanged request. Rejected customers may repeatedly increase their offer or explore the auction. Exploration reveals the guaranteed price and offers direct booking or official auction entry; exploration alone does not enroll them.
Require a rejected offer before auction entry. Starting bid = highest rejected offer. Every move qualifies regardless of size, volume, distance, cost, profitability, or rejected amount. No additional minimum auction bid.
5. Customer Access
Allow moving details, pricing, and offers without registration/login. Generate a unique customer ID when the process starts. Collect email and phone at booking commitment or official auction entry without initial password or verification requirements.
Returning customers verify either email or phone with a secure single-use code. Include expiration, resend, failed-attempt protection, logout, and protected sessions. Restore saved records across visits/devices. Do not expose or merge existing records solely because entered contact information matches.
6. Date Availability and Price Protection
Provide an admin calendar to block/unblock dates. Dates are available by default; bookings do not automatically reduce availability. Save availability when the customer selects a date. Later blocking must not invalidate that customer's saved selection; do not recheck it during offers, auctions, or confirmation.
Check voluntarily selected replacement dates when selected. Date-only changes preserve accepted, guaranteed, or winning prices. Recalculate when inventory/address changes affect volume or distance.
7. Auctions and Dashboard
One shared auction per moving date. Defaults: open 14 days before moving day, run 48 hours, close 12 days before moving day. Provide admin-editable schedules and synchronized backend timestamps/countdowns.
Support Upcoming, Live, and Completed states. Allow tokens before/during auctions and bid increases without decreases.
Auction Score = (Current Bid / Customer's Guaranteed Price x 100) + Approved Tokens.
Each approved token adds one percentage point. Automatically update scores/rankings. Show date, status, countdown, bid, guaranteed price, tokens, score, ranking, participation information, results, and booking actions. Freeze final bids/scores/tokens at close.
8. Winners and Reservations
Highest score wins; equal scores use higher dollar bid. Exact score/bid ties require manual admin resolution before announcing a winner. Initial confirmation window: 24 hours; reminder: eight hours. Both are admin-editable.
Expire unconfirmed opportunities and offer them sequentially to the next eligible customer at their own final bid, with a fresh window. Prevent duplicate winning reservations. Record no confirmed winner if exhausted. Auctions remain valid with one real customer; non-winners retain guaranteed-price booking.
Use one reservation system for accepted offers, guaranteed prices, winners, and replacement winners. Apply equal operational priority across booking methods.
9. Referral Tokens and Internal Profiles
Build Earn Tokens with own-post submissions, friends/family invitations, prepared promotional content, and personalized referral links. Friends/family submit without accounts. Associate every submission with the correct customer/auction.
Show Pending, Approved, and Rejected statuses. Admin manually reviews posts. Approval awards one token once and updates scores/rankings. Block duplicate normalized URLs/awards, preserve review history, stop submissions at closing, and prevent late approvals from changing results.
Provide reusable platform-controlled promotional profiles with unique IDs, active status, private notes, and independent per-auction bids, guaranteed-price references, tokens, scores, and status. Allow creation, editing, duplication, activation/deactivation, and assignment/removal. Preserve history, clearly label customer-visible profiles as platform-controlled, and exclude them from customer booking awards.
10. White-Label Partners and Discounts
Use one reusable landing template within the same Bubble app for unlimited partners with dedicated URL paths. Support configurable partner branding, contact fields, and descriptions.
Preserve partner branding/attribution through inventory, pricing, offers, auctions, tokens, dashboards, booking, and returning access. Regular customers retain the standard presentation. Reuse the same catalog, AI, routing, pricing, auction, and reservation systems.
Recognize active partner URLs automatically or validate unique promotional codes, including codes entered on the regular site. Recognized visitors need no code. Both discount stages use the original traditional price: initial 15% reduction plus another 15 percentage points, totaling 30%. Do not compound or apply twice; enforce confidential minimum pricing. Preserve the applicable booking price without another discount. No partner scoring bonuses.
11. Partner Administration and Portal
Provide no-code management of partner records, branding, contacts, descriptions, unique slugs/codes, active status, authorized portal email, access, and statistics visibility.
Track visits, attributed quote requests, and confirmed bookings separately. Count visits, not unique visitors; avoid duplicate quote/booking counts.
Build a separate password-authenticated partner portal in the same app. Partners see only their own branding, landing URL, and all-time visits when enabled. Access and statistics switches are independent. Enforce privacy rules preventing access to customers, inventory, quotes, bookings, auctions, revenue, conversions, other partners, or admin controls.
12. Notifications and Payments
Integrate client-controlled email/SMS for upcoming auctions, starts/results, confirmation reminders, replacement opportunities, and booking confirmations. Provide editable templates, schedules, switches, delivery records, and duplicate prevention. Private links require authorized sessions or passwordless verification.
No website payments, deposits, checkout, payment forms, or payment links. Payment occurs outside the site after completion, before movers leave, through an authorized representative using Venmo, Zelle, or credit card with a 5% fee.
13. Administration, Ownership, and Delivery
Provide catalog, pricing, calendar, auction, referral, booking, mover-assignment, partner, reporting, and export controls. Assignment is manual; customers see assigned provider/contact information while internal notes/history stay private. No mover-facing auction, automated payouts, or automatic assignment/change messages.
All website copy must be editable through the admin backend without code.
Build in client-controlled accounts with individual, restricted, revocable developer access. Obtain approval before adding plugins, extensions, APIs, or other dependencies; disclose costs. Required accounts/licenses must remain client-controlled. Maintain a dependency/access inventory and document databases, workflows, and integrations. Deliver external source code to a client-controlled private repository.
Demonstrate working features; test calculations, auctions, reassignment, duplicates, privacy, notifications, date preservation, partner attribution, and mobile operation. Provide documentation/training and correct agreed-scope audit findings before final acceptance.
Confirm complete regular/white-label scope, development price, timeline, integrations, ongoing costs, and any exclusions or clarification requirements.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.