Home

Use cases

docteurklein's use cases

• A customer can validate an order by:
  • pushing it in a stack, and generate an invoice at the end of the month
  • paying directly with a credit card ( a bank gateway ) -- and thus finalize the order
  • sending a check at mentioned address.
  • paying with promo codes, payback ( points won when paying other orders )

Inspiran's use cases

• Manufacturer-distributor with different customer groups
• Business to business product selling (eg. office supplies)
• Manufacturer of electronic components (eg. maxim-ic.com)
• Pre-order goods (eg. pre-order a game which is released withing a few weeks)

IamPersistent's use cases

• Digital-download
• Subscription service
• Pizza shop
• Customer pick up
• Targeted catalog
• Manufacturer fulfillment
• Remote fulfillment
• Affiliate links

alecslupu's use cases

• Comunication service
• User ACL system

Lufi use caes

• Clothing store

aalbagarcia's use cases

• API for integration with ERP/CMS systems. This API will provide ways to create and modify customers, orders and the catallogue itself.

rechengehirn's use cases

• Individualized products
• EAN handling
• Third-Party Deals
• Integration with other malls
• Workflow rules

alexanderdean's use cases

• A shopping basket that can be embedded on non-Vesponila pages (this for me is one of the strongest reasons for using a Symfony-based e-commerce tool rather than a standalone e-commerce package like Magento or Prestashop)

motheikle's use cases

• Viewable Product

developer's use case

• A developer wants to download the package and see an example shop running straight away with no fuss and full example fixture data, like Magento. This helps the developer to dive into the code to see whether it would be suitable for him to use on his next project.