Client Profile :
The company is dedicated to designing intelligent dispensing solutions and products that drive wine revenues, operating control, and growth in the restaurant, retail, entertainment, and hospitality industries.
The company has used vTiger since 2005.
The company originally had CRM customized through vTiger directly.
Project Screenshot

[dt_slideshow width=”800″ height=”450″ posts=”wine-machine”]

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.
  • The company wants to migrate from an older version of vTiger CRM to a new version.
Implementation :
The CRMTiger team is dedicated to working on the implementation of vTiger® CRM migration.
1. vTiger Migration
CRMTiger successfully migrated from the existing vTiger 5.2.0 to 5.3.0, with customization done so far in vTiger 5.2.0.
Process CRMTiger follows:
  • Take a backup of the existing version with a database on the safer side at the client end.
  • Implement migration on the staging server first and provide a URL to the client for testing.
  • The client tested the version and approved it on the staging server.
  • Client and team variance decided off time to move the new version on live link to the existing database.
  • Finally, the team migrates from an older version to a newer version.
The CRMTiger team is dedicated to working on the 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 the 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 the product bundle scenario above

  1. In the product module, we added “Bundle Quantity,” which is used to specify how much quantity of the product is needed to create a parent bundle. This quantity must be specified by the user when adding a product to the vTiger system.

  2. Stock Management

PO (purchase order)

  1. As per the client requirement, stock of the line item product has increased when the status of the PO is marked as “received shipment.”

  2. To do that, we use a recursive loop to calculate the stock because we have a tree structure for the products, as some products are under the parent product and the same product is the parent of another product.

SO (sales order)

  1. As per the client requirement, stock of the line item product has increased when the status of the SO mark is “shipped.”

  2. To do that, we use a recursive loop to calculate the stock because we have a tree structure for the products, as some products are under the parent product and the same product is the parent of another product.

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

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