# BEDDING E-COMMERCE STORE
## Master MVP Development Prompt

You are acting as a world-class e-commerce product development team consisting of:

- Senior Business Analyst
- Product Manager
- E-commerce Solution Architect
- Senior WordPress Developer
- Senior WooCommerce Developer
- Senior UI/UX Designer
- Senior Frontend Developer
- Senior Backend/PHP Developer
- Database Specialist
- QA Engineer
- Security Engineer
- DevOps/Deployment Engineer
- SEO Specialist
- Conversion Rate Optimization Specialist

Your objective is to design, develop, test and prepare for production a **professional Pakistani bedding e-commerce website using WordPress + WooCommerce**.

The objective is NOT to build a generic WooCommerce website.

The objective is to build a **production-ready MVP for a real bedding brand** that can go live and start accepting orders.

---

# 1. BUSINESS MODEL

The business operates using a low-inventory/on-demand fulfillment model.

The business owner does not maintain a separate warehouse.

Products are available through a nearby factory/store.

Customer:

1. Visits website
2. Selects product
3. Adds product to cart
4. Checks out
5. Selects Cash on Delivery or online payment
6. Receives order confirmation
7. Order is fulfilled through the factory/store
8. Courier collects/delivers the order
9. COD amount is settled with the business

The system must therefore prioritize:

- Product presentation
- Conversion
- COD
- Order verification
- Fulfillment
- Courier tracking
- Customer communication
- Marketing analytics
- Simple administration

Do NOT build unnecessary enterprise functionality.

---

# 2. TARGET MARKET

Primary market:

Pakistan.

The website must be:

- Mobile-first
- Fast
- Simple
- Trustworthy
- Conversion-focused
- COD-friendly
- Optimized for Pakistani customers
- Compatible with Pakistani cities and addresses

Currency:

PKR / Rs.

Language:

English initially, but architecture should allow Urdu localization later.

---

# 3. INITIAL PRODUCT CATALOG

The initial product catalog consists of:

## BED SHEETS

- Cotton
- Sotten
- Fleece
- Fancy / Bridal
- Plain
- Fitted
- Waterproof

## BLANKETS

- Fleece Blankets
- Blankets

## BEDDING SETS

- Bedsheet Sets
- Razai Sets

## PILLOWS

- Pillows

Do not invent additional product categories unless required by the business logic.

---

# 4. PRODUCT CATEGORY ARCHITECTURE

Use a clean taxonomy.

Primary categories:

BED SHEETS
- Cotton
- Sotten
- Fleece
- Fancy / Bridal
- Plain
- Fitted
- Waterproof

BLANKETS
- Fleece Blankets
- Blankets

BEDDING SETS
- Bedsheet Sets
- Razai Sets

PILLOWS

Products should also support attributes such as:

- Fabric
- Size
- Color
- Pattern
- Season
- Set type
- Thickness
- Dimensions

Avoid excessive taxonomy complexity.

---

# 5. BRAND EXPERIENCE

The website must NOT look like a default WooCommerce installation.

Do not use a generic WooCommerce theme appearance.

Create a custom visual design system.

The design should feel:

- Premium
- Modern
- Warm
- Comfortable
- Trustworthy
- Fashionable
- Pakistani-market appropriate
- Visually rich

Avoid:

- Plain white generic layouts
- Excessive gradients
- Excessive animations
- Cheap marketplace appearance
- Cluttered interfaces
- Excessive popups
- Excessive badges
- Fake urgency
- Fake discounts

The customer should feel they are buying from a real bedding brand.

---

# 6. DESIGN SYSTEM

Before implementing the complete frontend, establish:

- Color palette
- Typography
- Font hierarchy
- Spacing system
- Border radius system
- Button system
- Card system
- Form system
- Icon system
- Responsive breakpoints
- Product image standards
- Trust badge style
- Notification style

Create a reusable design system.

Do not duplicate CSS unnecessarily.

Use reusable components/templates.

---

# 7. HOMEPAGE

Create a premium conversion-focused homepage.

Sections:

1. Header
2. Hero banner
3. Primary CTA
4. Featured categories
5. Best sellers
6. Featured collection
7. Shop by product type
8. Shop by need/occasion
9. Why choose us
10. Customer reviews
11. Promotional section where appropriate
12. Social proof
13. Newsletter/WhatsApp CTA if useful
14. Footer

The homepage must prioritize:

- Product discovery
- Trust
- Conversion
- Mobile usability

---

# 8. HEADER

Desktop:

- Logo
- Shop
- Bed Sheets
- Blankets
- Bedding Sets
- Pillows
- Search
- Account
- Cart

Mobile:

- Menu
- Logo
- Search
- Cart

Header should remain usable on small screens.

Do not create a huge complicated mega menu for MVP.

---

# 9. PRODUCT LISTING PAGE

Product listing pages must support:

- Product grid
- Pagination or optimized loading
- Sorting
- Filtering
- Search
- Category navigation

Filters:

- Price
- Category
- Fabric
- Size
- Color
- Pattern
- Availability

Sorting:

- Popular
- Newest
- Price low to high
- Price high to low

Product card must display:

- Product image
- Product name
- Price
- Sale price if applicable
- Rating where available
- Basic product attribute
- Add to cart

Do not overload product cards.

---

# 10. PRODUCT DETAIL PAGE

The product page is a critical conversion page.

Include:

- Product name
- Product gallery
- Product video where available
- Price
- Sale price
- Discount where legitimate
- Product availability
- Variations
- Size selection
- Color selection
- Quantity
- Add to cart
- Buy now
- COD availability
- Delivery information
- Product description
- Product specifications
- What's included
- Care instructions
- Size information
- Return/exchange policy
- Customer reviews
- Related products

Use structured sections rather than giant blocks of text.

---

# 11. PRODUCT INFORMATION

Every product should support structured information.

Example:

Fabric:
Cotton

Size:
King

Dimensions:
[configured per product]

Pieces:
3

Includes:
1 bedsheet + 2 pillow covers

Pattern:
Floral

Season:
Summer

Care:
Machine washable

Do not hard-code product specifications.

They must be manageable from WooCommerce admin.

---

# 12. PRODUCT VARIATIONS

WooCommerce variable products should be used where necessary.

Examples:

Size:

- Single
- Double
- Queen
- King

Color:

- White
- Beige
- Blue
- Pink
- etc.

Do not create separate products for every variation unless there is a genuine business requirement.

---

# 13. CART

Cart must be simple.

Display:

- Product
- Image
- Variation
- Quantity
- Unit price
- Subtotal
- Remove
- Cart total
- Shipping
- Grand total

CTA:

Proceed to Checkout

Do not force account registration.

---

# 14. CHECKOUT

Guest checkout must be enabled.

Required information should be minimal.

Customer:

- Full name
- Mobile number
- Email optional

Shipping:

- Province
- City
- Area
- Complete address
- Landmark optional

Payment:

- Cash on Delivery
- Configurable online payment gateway

Do not request unnecessary information.

Optimize checkout for mobile.

---

# 15. CASH ON DELIVERY

COD is a primary payment method.

The system must support:

- COD order creation
- COD verification
- COD status
- COD collection
- COD settlement

Recommended order workflow:

Pending
→ Verification Required
→ Confirmed
→ Fulfillment
→ Shipped
→ Out for Delivery
→ Delivered
→ COD Collected
→ Settlement Received

Support:

- Cancelled
- RTO
- Returned
- Refunded

Do not create unnecessary order statuses.

---

# 16. COD VERIFICATION

Create a mechanism for order verification.

MVP may support:

- Manual verification by admin
- WhatsApp confirmation
- SMS confirmation if an integration is configured

For higher-value orders, allow the admin to mark:

Verification Required

The admin must be able to record:

- Verification status
- Verification date
- Verification notes

Do not implement complex AI fraud detection in MVP.

---

# 17. ONLINE PAYMENTS

Payment gateway must be configurable.

Architecture must allow integration with a Pakistan-compatible payment provider.

Do not build payment processing from scratch.

Store:

- Gateway
- Transaction ID
- Payment status
- Payment date
- Amount

Statuses:

- Pending
- Paid
- Failed
- Refunded

Never store raw card information.

---

# 18. ORDER MANAGEMENT

Admin must have a dedicated order management experience.

Order list:

- Order ID
- Date
- Customer
- Total
- Payment
- Fulfillment status
- Courier
- Tracking
- Order status

Filters:

- New
- Verification
- Confirmed
- Fulfillment
- Shipped
- Delivered
- Cancelled
- RTO
- Returned

Admin should be able to update orders quickly.

---

# 19. ORDER DETAIL

Order detail must show:

Customer information

Shipping address

Products

Variations

Quantity

Price

Discount

Shipping

Total

Payment method

Payment status

Courier

Tracking number

Order status

Order notes

Verification status

COD status

Timeline/history

---

# 20. PRODUCT ADMINISTRATION

Admin must be able to:

- Add product
- Edit product
- Delete product
- Duplicate product
- Publish/unpublish product
- Set price
- Set sale price
- Add images
- Add gallery
- Configure variations
- Configure attributes
- Configure categories
- Set stock status
- Set SKU
- Add SEO information

Product status:

- Published
- Draft
- Out of stock
- Private

---

# 21. INVENTORY APPROACH

This business does not maintain its own warehouse in MVP.

Therefore DO NOT build a complex inventory system.

Use WooCommerce stock functionality where useful.

At minimum support:

- In stock
- Out of stock

Optionally support:

- Limited availability

The factory remains the physical source of inventory.

Future versions may integrate factory stock.

---

# 22. FULFILLMENT

MVP fulfillment workflow:

Order confirmed
→ Fulfillment pending
→ Packed
→ Ready for courier
→ Shipped

Admin must be able to update fulfillment status.

The system should clearly identify orders that need factory/store fulfillment.

Do not create a separate factory portal in MVP unless implementation is trivial.

Architecture should allow one to be added later.

---

# 23. COURIER

MVP should support manual courier assignment.

Store:

- Courier name
- Tracking number
- Shipment date
- Delivery status

Architecture must allow future courier API integration.

Future:

WooCommerce
→ Courier API
→ Shipment creation
→ Tracking number
→ Tracking updates

Do not implement multi-courier optimization in MVP.

---

# 24. CUSTOMER MANAGEMENT

Admin must be able to view:

- Customer name
- Mobile
- Email
- Address
- Orders
- Total orders
- Total spent
- Cancelled orders
- Returned/RTO orders

Show customer order history.

---

# 25. CUSTOMER ACCOUNT

Customers may optionally create an account.

Account dashboard:

- Profile
- Addresses
- Orders
- Order details
- Account information

Guest checkout remains available.

---

# 26. COUPONS

MVP supports:

- Percentage discount
- Fixed amount discount
- Minimum order value
- Expiry date
- Usage limit
- Product/category restriction

Examples:

WELCOME10
FIRSTORDER
EID20

---

# 27. REVIEWS

Support:

- Star rating
- Text review
- Optional photo

Admin moderation:

- Approve
- Reject
- Delete

Verified purchasers should receive a:

Verified Purchase

indicator.

---

# 28. SHIPPING

MVP:

- Pakistan-wide shipping
- Configurable shipping fee
- Free shipping threshold
- Optional city-specific shipping rules

Admin must be able to configure shipping from WooCommerce.

Do not build advanced logistics pricing in MVP.

---

# 29. NOTIFICATIONS

Customer notifications:

1. Order received
2. Order confirmed
3. Order shipped
4. Order delivered
5. Order cancelled where applicable

Use WooCommerce email functionality initially.

Architecture should allow:

- WhatsApp
- SMS

to be integrated later.

---

# 30. ADMIN DASHBOARD

Create a simplified business dashboard.

Show:

Orders Today
Sales Today
Pending Verification
Orders to Fulfill
Orders Shipped
Orders Delivered
RTO
Cancelled Orders

Sales:

- Today
- This week
- This month

Products:

- Best sellers
- Low/out-of-stock products

Do not replace the complete WooCommerce admin unnecessarily.

Create only the custom dashboard functionality that improves operations.

---

# 31. BUSINESS ANALYTICS

Track:

- Orders
- Gross sales
- Net sales
- Average order value
- Delivered orders
- Cancelled orders
- RTO orders
- Return rate
- Product sales
- Category sales

Prepare architecture for:

- CAC
- ROAS
- Contribution margin

Marketing analytics should be integrated with:

- Google Analytics
- Meta Pixel

---

# 32. SEO

Implement:

- Clean URLs
- SEO-friendly product URLs
- Category URLs
- Meta titles
- Meta descriptions
- Canonical URLs
- XML sitemap
- Product schema
- Breadcrumb schema
- Open Graph
- Image alt text
- Proper heading structure

Ensure pages are indexable.

---

# 33. PERFORMANCE

Performance is a priority.

Target:

- Fast mobile loading
- Optimized images
- Lazy loading
- Minimal JavaScript
- Minimal plugins
- Browser caching
- CSS optimization
- WebP/modern image formats where appropriate

Do not install plugins merely because they provide functionality that can be implemented cleanly without them.

---

# 34. SECURITY

Implement:

- SSL/HTTPS
- Secure admin authentication
- Strong password policy
- WordPress security best practices
- Nonce validation
- Input sanitization
- Output escaping
- Capability checks
- Secure AJAX endpoints
- Secure payment handling
- No card data storage
- Regular backup compatibility

Never expose sensitive information.

---

# 35. RESPONSIVE DESIGN

The website must work properly on:

- Mobile phones
- Tablets
- Laptops
- Desktop
- Large desktop screens

Mobile is the primary consideration.

Test at minimum:

360px
390px
430px
768px
1024px
1440px

---

# 36. ADMIN ROLES

Use WordPress/WooCommerce permissions.

At minimum:

Administrator

Store Manager

Future:

Fulfillment Staff

Customer Support

Do not give unnecessary administrator permissions to operational staff.

---

# 37. DATA MODEL

Use WooCommerce's native product/order/customer structures wherever possible.

Do not duplicate WooCommerce data unnecessarily.

Custom data should only be introduced where the business requires it.

Possible custom fields:

- COD verification status
- COD verification notes
- Fulfillment status
- Courier
- Tracking number
- COD collection status
- Settlement status

Avoid creating a custom order system beside WooCommerce.

WooCommerce remains the source of truth for commerce.

---

# 38. PLUGIN STRATEGY

Do not install dozens of plugins.

For every plugin:

1. Determine whether WooCommerce already provides the feature.
2. Determine whether WordPress provides the feature.
3. Determine whether a small custom implementation is safer.
4. Only then install a third-party plugin.

Every plugin must be evaluated for:

- Security
- Performance
- Compatibility
- Maintenance
- Licensing
- Vendor reliability

Avoid plugin bloat.

---

# 39. DEVELOPMENT PROCESS

Follow this sequence.

## STEP 1 — BUSINESS ANALYSIS

Create:

BUSINESS_REQUIREMENTS.md

Include:

- Business model
- Personas
- User journeys
- Functional requirements
- Non-functional requirements
- Business rules
- MVP boundaries
- Future requirements

## STEP 2 — INFORMATION ARCHITECTURE

Create:

INFORMATION_ARCHITECTURE.md

Include:

- Sitemap
- Categories
- Product taxonomy
- Navigation
- Customer journey

## STEP 3 — UX

Create:

UX_SPECIFICATION.md

Include:

- User journeys
- Wireframe descriptions
- Checkout flow
- Product discovery flow
- Order flow

## STEP 4 — UI

Create:

DESIGN_SYSTEM.md

Include:

- Colors
- Typography
- Components
- Buttons
- Cards
- Forms
- Responsive behavior

## STEP 5 — TECHNICAL ARCHITECTURE

Create:

TECHNICAL_ARCHITECTURE.md

Document:

- WordPress architecture
- WooCommerce
- Theme structure
- Custom plugin structure
- Database usage
- Integrations
- Security
- Performance

## STEP 6 — DEVELOPMENT

Build the website incrementally.

Do not generate the entire system blindly in one pass.

After each major module:

- Test
- Review
- Fix
- Document

---

# 40. CUSTOM CODE ARCHITECTURE

Keep custom business logic separate from the theme where possible.

Use:

Custom theme
+
Custom business plugin

Do not put critical business logic into random theme files.

Recommended conceptual structure:

/wp-content/themes/brand-theme/

/wp-content/plugins/brand-commerce/

Separate:

- Presentation
- Business logic
- WooCommerce customizations
- Integrations

Follow WordPress and WooCommerce coding standards.

---

# 41. QA

Before launch, test:

## CUSTOMER

- Homepage
- Navigation
- Search
- Category
- Product
- Variations
- Cart
- Checkout
- COD
- Online payment
- Account
- Order history

## ADMIN

- Product creation
- Product editing
- Categories
- Variations
- Orders
- Customers
- Coupons
- Reviews
- Fulfillment
- Courier
- Tracking
- Dashboard

## EDGE CASES

- Out of stock
- Invalid phone
- Invalid address
- Failed payment
- Duplicate checkout
- Cancelled order
- RTO
- Returned order
- Coupon failure
- Incorrect variation
- Large quantity order

---

# 42. LAUNCH CHECKLIST

Do not declare the project complete until:

- Domain works
- HTTPS works
- WordPress configured
- WooCommerce configured
- Products work
- Categories work
- Search works
- Filters work
- Cart works
- Checkout works
- COD works
- Online payment works
- Order emails work
- Admin works
- Customer account works
- Courier tracking can be recorded
- Analytics installed
- Meta Pixel installed
- SEO configured
- Sitemap works
- Mobile tested
- Desktop tested
- Security checked
- Backup configured
- Performance tested

---

# 43. MVP SUCCESS CRITERIA

The MVP is successful when a real customer can:

1. Discover a product
2. Understand the product
3. Select the correct variation
4. Add it to cart
5. Checkout without registration
6. Select COD
7. Place an order
8. Receive confirmation

And the business owner can:

1. See the order
2. Verify it
3. Confirm it
4. Fulfill it through the factory
5. Assign courier
6. Add tracking
7. Track delivery
8. Record COD collection
9. Manage products
10. View sales

If all of this works reliably, the MVP is ready for production.

---

# 44. IMPORTANT MVP DISCIPLINE

Do not expand the scope without explicit approval.

If a requested feature is not required for:

- Customer purchase
- Product management
- Order management
- Payment
- Fulfillment
- Delivery
- Basic marketing analytics

classify it as:

FUTURE FEATURE

Do not automatically implement it.

Prioritize:

1. Reliability
2. Simplicity
3. Conversion
4. Performance
5. Maintainability
6. Security

over feature count.

---

# 45. FINAL PRODUCT PRINCIPLE

Build a website that makes the customer think:

"These products look trustworthy, I understand what I am buying, ordering is easy, COD is available, and I can trust this brand."

Build an admin system that makes the owner think:

"I can manage my entire daily e-commerce operation from one place without technical knowledge."

The MVP should be **simple enough to launch quickly but architected correctly enough to scale later.**

Do not over-engineer.

Do not build a marketplace.

Do not build an ERP.

Do not build a mobile app.

Build a **high-quality, custom-designed Pakistani bedding e-commerce store powered by WooCommerce that can go live and start generating real orders.**