CASE STUDY For Wine Machine

Client Profile :
Company is dedicated to designing Intelligent Dispensing Solutions and Products that drive wine revenues, operating control, and growth for the Restaurant, Retail, Entertainment, and Hospitality industries.
Company uses vTiger since 2005.
Company originally had CRM customized through vTiger directly.
Project Screenshot

  • press-automation-company

  • vtiger-wine-station

  • electronic-suppliers

  • sav-lite


Business Needs:
vTiger Migration:
  • Company looking to have prior customizations ported to a newer software version as well as having a few additional customizations done.
  • Company wants to migrate from older version of vTiger CRM to new version.
Implementation :
CRMTiger team dedicated working on Implementation of vTiger® CRM migration.
1. vTiger Migration
CRMTiger successfully migrated from existing vTiger 5.2.0 to 5.3.0 with customization done so far in vTiger 5.2.0
Process CRMTiger follows:
  • Take the backup of existing version with database on safer side at client end
  • Implement migration on staging server first and provided URL to client for testing.
  • Client tested the version and approved it on staging server.
  • Client and Team variance decided off time to move new version on live link to existing database.
  • Finally team migrates from older version to newer version.
CRMTiger team dedicated working on Implementation of vTiger® CRM migration.
2. Business Needs
vTiger Customization Requirement from client on new version :
Product Bundles
  1. We must have the ability to add bundles within bundles. And then add those bundles within other bundles.
  2. Individual parts and parts within bundles will be used in both purchase orders and sales orders.
  3. Bundles within bundles (and those within more bundle levels) will be used in sales orders only.
Purchase Orders
  1. Any PO’s created that has a bundle will reduce stock of the parts in bundle upon creation.
  2. Parts that are sold individually and in bundles will have separate part numbers created. Stock will be moved from the part not in a bundle to the part that is in a bundle as needed.
Implementation :
Implementation steps to implement product bundle scenario above
  1. In product module we added “Bundle Quantity” which use to specify how much quantity of the product needed to create parent bundle. This quantity user has to specify when add product in vTiger system

  2. Stock Management

PO (Purchase order)
  1. As per the client requirement Stock of the line item product has been increase when status of the PO mark as “Received shipment”

  2. To do that we use recursive loop to calculate the stock because we have tree structure of the product as some product is under parent product and same product is the parent of other product.

SO (Sales order)
  1. As per the client requirement Stock of the line item product has been increase when status of the SO mark as “shipped”

  2. To do that we use recursive loop to calculate the stock because we have tree structure of the product as some product is under parent product and same product is the parent of other product.

Tools and Technology :
  • vTiger® version 5.4
  • PHP 5.3
  • MYSQL
  • SMARTY Framework

Do You Need More Information ?
For any further information / query regarding CRM, please email us at info@crmtiger.com
OR call us on +1 630 861 8263, Alternately you can request for information by filling up Contact Us