Vamvaki B2B Apparel Website Development
Budget: $250 – $750 AUD
Vamvaki B2B Website Requirements and Technical Specification
Document Purpose
This document defines the functional, technical, architectural, and operational requirements for the Vamvaki B2B website. The platform will position Vamvaki as a branded corporate apparel provider with manufacturing capability and structured wholesale operations. The website will support tiered pricing, MOQ enforcement, domain-restricted catalogue access, manufacturing options, and structured product documentation.
1. Business Objectives
• Position Vamvaki as a professional corporate apparel brand.
• Support wholesale and manufacturing workflows.
• Enforce tiered pricing and MOQ per style and per colour.
• Restrict pricing visibility to registered and approved trade users.
• Enable domain-based product visibility and role control.
• Support custom logo uploads and garment specification documentation.
• Provide a corporate presentation standard comparable to leading industry brands.
2. Platform Architecture
Core Platform Stack:
• WordPress
• WooCommerce
• Porto Premium Theme
• B2BKing Pro
• WooCommerce Product Add-Ons or equivalent
• SMTP email infrastructure for domain verification
3. User Access Model
3.1 Public Visitors
• Product catalogue visible without pricing.
• No Add to Cart functionality.
• Call to Action: Register for Trade Access.
3.2 Registered Trade Users
• Pricing visible after login.
• Tiered pricing tables visible.
• MOQ enforcement enabled.
• Add to Cart and Checkout enabled.
3.3 Domain Restricted Access
• Users registering with approved business domains are auto-assigned specific roles.
• Certain product categories are visible only to specific roles.
• Role assignment triggered after email verification.
• Admin approval workflow configurable.
4. Registration and Verification Workflow
• Business registration form capturing Company Name, ABN, Position, Email, Phone.
• Email verification link sent to domain email.
• Domain extracted and matched against predefined mapping.
• Role assigned automatically based on domain.
• Optional manual approval by administrator before activation.
5. Product Architecture
5.1 Parent Product Structure
• Each garment represented as a base style product.
• Variations include Colour and Size.
• Decoration options available as configurable add-ons.
5.2 Colour Logic
• Stock colours available for immediate dispatch.
• Made-to-order colours with MOQ 300 per colour per style.
• Custom Pantone manufacturing options with higher MOQ.
• Lead time displayed per colour category.
5.3 MOQ Enforcement
• Minimum order quantity enforced at variation level.
• Custom colour variations require MOQ 300.
• System prevents checkout below defined MOQ.
• Option to enforce pack multiples where required.
6. Pricing Model
• Pricing hidden from guests.
• Tiered pricing per product displayed after login.
• Fixed wholesale tier pricing preferred over percentage discounting.
• Ability to support future customer-specific contract pricing.
7. Logo Upload and Customisation
• File upload field per product supporting AI, EPS, PDF, PNG.
• Decoration position selector.
• Thread or print colour notes field.
• Optional artwork setup fee logic.
• Files stored securely and attached to order record.
8. Product Documentation
Per product documentation includes:
• Fabric composition
• GSM
• Care instructions
• Downloadable PDF care sheet
• Size chart PDF
• Decoration suitability guidelines
9. User Experience Design Principles
• Corporate, clean layout.
• No retail sale banners or discount language.
• Swatch-based colour selection.
• Structured technical specification sections.
• Professional photography and consistent imagery.
10. Email Infrastructure
• SMTP configured via SendGrid, Amazon SES, or Microsoft 365.
• SPF and DKIM configured for deliverability.
• Email verification mandatory before role assignment.
11. Scalability Considerations
• Future onboarding of additional distributors.
• Role-based catalogue expansion.
• Customer-specific pricing tiers.
• Support for credit accounts and Net terms.
• Purchase order upload capability.
• Downloadable price lists per role.
12. Security and Compliance
• Secure file upload validation.
• Role-based access control.
• GDPR and Australian privacy compliance alignment.
• Secure hosting with SSL enforced.
• Regular backups and maintenance plan.
Document Purpose
This document defines the functional, technical, architectural, and operational requirements for the Vamvaki B2B website. The platform will position Vamvaki as a branded corporate apparel provider with manufacturing capability and structured wholesale operations. The website will support tiered pricing, MOQ enforcement, domain-restricted catalogue access, manufacturing options, and structured product documentation.
1. Business Objectives
• Position Vamvaki as a professional corporate apparel brand.
• Support wholesale and manufacturing workflows.
• Enforce tiered pricing and MOQ per style and per colour.
• Restrict pricing visibility to registered and approved trade users.
• Enable domain-based product visibility and role control.
• Support custom logo uploads and garment specification documentation.
• Provide a corporate presentation standard comparable to leading industry brands.
2. Platform Architecture
Core Platform Stack:
• WordPress
• WooCommerce
• Porto Premium Theme
• B2BKing Pro
• WooCommerce Product Add-Ons or equivalent
• SMTP email infrastructure for domain verification
3. User Access Model
3.1 Public Visitors
• Product catalogue visible without pricing.
• No Add to Cart functionality.
• Call to Action: Register for Trade Access.
3.2 Registered Trade Users
• Pricing visible after login.
• Tiered pricing tables visible.
• MOQ enforcement enabled.
• Add to Cart and Checkout enabled.
3.3 Domain Restricted Access
• Users registering with approved business domains are auto-assigned specific roles.
• Certain product categories are visible only to specific roles.
• Role assignment triggered after email verification.
• Admin approval workflow configurable.
4. Registration and Verification Workflow
• Business registration form capturing Company Name, ABN, Position, Email, Phone.
• Email verification link sent to domain email.
• Domain extracted and matched against predefined mapping.
• Role assigned automatically based on domain.
• Optional manual approval by administrator before activation.
5. Product Architecture
5.1 Parent Product Structure
• Each garment represented as a base style product.
• Variations include Colour and Size.
• Decoration options available as configurable add-ons.
5.2 Colour Logic
• Stock colours available for immediate dispatch.
• Made-to-order colours with MOQ 300 per colour per style.
• Custom Pantone manufacturing options with higher MOQ.
• Lead time displayed per colour category.
5.3 MOQ Enforcement
• Minimum order quantity enforced at variation level.
• Custom colour variations require MOQ 300.
• System prevents checkout below defined MOQ.
• Option to enforce pack multiples where required.
6. Pricing Model
• Pricing hidden from guests.
• Tiered pricing per product displayed after login.
• Fixed wholesale tier pricing preferred over percentage discounting.
• Ability to support future customer-specific contract pricing.
7. Logo Upload and Customisation
• File upload field per product supporting AI, EPS, PDF, PNG.
• Decoration position selector.
• Thread or print colour notes field.
• Optional artwork setup fee logic.
• Files stored securely and attached to order record.
8. Product Documentation
Per product documentation includes:
• Fabric composition
• GSM
• Care instructions
• Downloadable PDF care sheet
• Size chart PDF
• Decoration suitability guidelines
9. User Experience Design Principles
• Corporate, clean layout.
• No retail sale banners or discount language.
• Swatch-based colour selection.
• Structured technical specification sections.
• Professional photography and consistent imagery.
10. Email Infrastructure
• SMTP configured via SendGrid, Amazon SES, or Microsoft 365.
• SPF and DKIM configured for deliverability.
• Email verification mandatory before role assignment.
11. Scalability Considerations
• Future onboarding of additional distributors.
• Role-based catalogue expansion.
• Customer-specific pricing tiers.
• Support for credit accounts and Net terms.
• Purchase order upload capability.
• Downloadable price lists per role.
12. Security and Compliance
• Secure file upload validation.
• Role-based access control.
• GDPR and Australian privacy compliance alignment.
• Secure hosting with SSL enforced.
• Regular backups and maintenance plan.