TechLogix IT

Global Services Pvt Ltd

MySQL to ZOHO
Strateworks Solutions

Version 1
9th Feb 2024
Proposal Number: TLP000005
Table of Contents

INTRODUCTION 3

HIGH LEVEL CONCEPT ARCHITECTURE 3

DELIVERY PROCESS 5
FEEDBACK BASED INCREMENTAL DELIVERY PROCESS(SCRUM) 5

PRODUCT BACKLOG 9

HIGH-LEVEL RELEASE PLAN 14

TIME AND COST MODEL 14

TERMS AND CONDITIONS 14

 Introduction
We provide custom web / software / app development solutions for our clients. We engage with our
clients in providing them with solutions that help them improve their business process and work more
efficiently. We use open source technologies. By leveraging the advantages of using an open source
technology, we are able to provide our clients cost saving through zero licensing fees when deploying
projects

High Level Technology Architecture

NodeJS Architecture

ReactJS Architecture

217, 2nd Floor, Golden Plaza, Mahatma Gandhi Rd, Opp. BSNL Office, Bharuch, 392001.
mobile: +91 76007 73889 | email: hello@techlogixit.com | website: https://www.techlogixit.com
 Proposed Solution Architecture

217, 2nd Floor, Golden Plaza, Mahatma Gandhi Rd, Opp. BSNL Office, Bharuch, 392001.
mobile: +91 76007 73889 | email: hello@techlogixit.com | website: https://www.techlogixit.com
 Proposal Outline

The following sections detail this proposal, starting with the customer-focused process under which
TechLogixIT Services delivers its services. The subsequent sections detail the problem statement
and a solution outline. Based on the information hence detailed after due deliberation, an
estimation of time and cost is arrived at towards the end of this document. A brief definition is
provided below of each section

⚫ Delivery Process The method and the manner in which The TechLogixIT delivers its service
⚫ Product Backlog Problem statement translated into a structured set of requirements
⚫ Solution Outline A note on the solution that The TechLogixIT will build to address the
problem
⚫ Specifications High level technical specifications of the solution
⚫ Time Model Estimated timeline in which the delivery of the solution will take place
⚫ Cost Model Components of the service and their corresponding estimated cost
⚫ Recommendations Recommendations in the interest of customer

DELIVERY PROCESS

217, 2nd Floor, Golden Plaza, Mahatma Gandhi Rd, Opp. BSNL Office, Bharuch, 392001.
mobile: +91 76007 73889 | email: hello@techlogixit.com | website: https://www.techlogixit.com
 Feedback based incremental delivery process(SCRUM)

TechLogixIT follows a customer-focused delivery process called SCRUM. From the left, any piece of
functionality is referred to as a User Story - an action and outcome that a user expects from the
system. Each User Story has various Acceptance Criteria. User stories are collaboratively defined by
all stakeholders. The full set of agreed and prioritized User Stories is called a prioritized Product
Backlog. The Product Backlog is curated by a designated officer from our team called the Product
Owner. The Product Backlog is implemented incrementally in fast 1 or 2 week cycles with a new,
shippable version ready at the end of every cycle. The weekly/bi-weekly cycle is called a Sprint. The
work done by the team within a sprint is supervised by a Scrum Master. The system version
produced at the end of every Sprint is called a Potentially Shippable Product Increment. The
customer reviews this increment and provides feedback. Feedback is refined, re-prioritized and
incorporated in future Sprints. Any increment can go live at the end of any Sprint based on the
customer’s assessment of whether it meets their immediate priorities. A Sprint can either be of 1
week or 2 weeks based on the context.

Project Scope
Objective of this project to sync mysql database to ZOHO book with the help our API utility
which mainly focused to pull data from end user client system and push same data via ZOHO
books APIs

• Review and prepare request and response for Item, Customer, Invoice & Bills APIs and submit
to client.
• Fetch pull APIs for Item, Customer, Invoice & Bills and manage in internal database and then
push into ZOHO Books via API
• Maintain Pushed records history with all status
• Create scheduler on every 1 hr Interval pull and push APIs will be performed.
• Maintain failed records
• Design Interface which has Pulled and pushed records view including below features
◦ Records History Interval wise
◦ User can change scheduler interval
◦ View failed and success records
◦ Delete history
◦ Action button Sync/Start & Stop for operations
◦ UI/UX
• Configuration of utility at client server
• Support as per Pay As You Go model based on hours
PRODUCT BACKLOG
This is a high level outline of the requirements.

1. Customer API

Client API Client Fields ZOHO API ZOHO Fields

TBD Type https: "contact_type"
//www.zoho.com/b
ooks/api/v3/contact
s/#create-a-
contact/custom_fiel
ds

Entity ID "contact_name"
Entity Number "contact_id"
Is Person "cf_Is_Person"
Individual "cf_Individual"
Term "payment_terms"
Client Category "cf_client_category"
Company Name "company_name"
First Name "first_name"
Middle Name "cf_middle_name"
Last Name "last_name"
Legal Name "contact_name"
Email "email"
Pan No.
Pan Availability "cf_pan_availability"
GST Reg Type "gst_treatment"
Address1 "billing_address
Address2 "billing_address"
GST NO "gst_no"
Address3 "cf_address3"
AddressID "cf_addressid"
Attention "attention"
Country "country"
Phone "phone"
 State "state"
City "city"
Zip "zip"

2. Item API

Client API Client Fields ZOHO API ZOHO Fields

TBD
https:
//www.zoho.com/books
/api/v3/items/#list-
items
Item Id "item_id"
Display Name "name"
Description "description"
Item Category "cf_item_category"
HSN_Code "hsn_or_sac”
COGS Account purchase_account_id"
Asset Account "inventory_account_id"
Product Type "product_type"

3. Invoice API

Client API Client Fields ZOHO API ZOHO Fields

TBD https:
//www.zoho.com/boo
ks/api/v3/invoices
Invoice No. "invoice_number"
Transaction for "cf_transaction_for"
Record Id "invoice_id"
Invoice date "date"
MRF Name "cf_mrf_name"
MRF NS ID "cf_mrf_ns_id"
Material Type "cf_material_type"
Other Reference "subject"
Client Code "customer_id"
Client Name "customer_name"
Client PO NO "cf_client_po_no"
Discount Amount "discount_amount"
Feright Amount "cf_feright_amount"
Gross Amount "cf_gross_amount"
Total Tax Amount "tax_total"
Net Amount "cf_net_amount"
Paid "cf_paid"
TCS "cf_tcs"
Eway Bill No.
Transporter Name "cf_transporter_name"
Dispatch from "cf_dispatch_from"
Dispatch to "cf_dispatch_to"
Dispatch Doc No. "cf_dispatch_doc_no"
Delivery Term "cf_delivery_term"
E Invoice No,
Ack Date "cf_ack_date"
Ack No, "cf_ack_no"
Craeted at "cf_created_at"
Updated at "cf_updated_at"
Class "cf_class"
Department "cf_department"
Product Name "name" "Hard Drive"
Product Code "item_id"
Product Description "description"
HSN Code "hsn_or_sac"
UOM
Product Rate "rate"
Sales Qty "quantity"
CGST Rate "tax_specific_type"
"string"
SGST Rate "tax_specific_type"
"string"
IGST Rate "tax_specific_type"
CGST "tax_specific_type"
 SGST "tax_specific_type"
IGST "tax_specific_type"
Gross Amount "sub_total"
Tax Amount "tds_tax_id"
Net Amount "total"
Summary ID "cf_summary_id"

4. Bills API

Client API Client Fields ZOHO API ZOHO Fields

TBD Record id https
://www.zoho.com/bo
oks/api/v3/invoices
Record Type "bill_id"
Collection type "cf_record_type"
Purchase type "cf_collection_type"
MRF "cf_purchase_type"
MRF ID "cf_mrf"
Vendor Id "cf_mrf_id"
Vendor Code "vendor_id"
Vendor Type Id "cf_vendor_code"
Vendor Type "cf_vendor_type_id"
Vendor Name "cf_vendor_type"
Vehicle Number "vendor_name"
Driver Name "cf_vehicle_number"
Driver Netsuite Code "cf_driver_name"
Payment Mode "cf_driver_netsuite_cod
e"
gst Name "cf_payment_mode"
Posting date "gst_treatment"
Vendor PO No. "cf_posting_date"
Tax Invoice Date "cf_vendor_po_no"
Challan no. "cf_tax_invoice_date"
Batch Code "cf_challan_no"
E Invoice number "cf_batch_code"
Paid "cf_paid"
 Material Type "cf_material_type"
Item Id "item_id"
Item Code "cf_item_code"
Item Name "name"
HSN Code "hsn_or_sac"
UOM "cf_uom"
Collection Qty "cf_collection_qty"
Net Qty "sub_total"
Item Price "total"
total value "total"
Item Class "cf_item_class"
Item Department "cf_item_department"
Class "cf_class"
Department "cf_department"
Summary id "cf_summary_id"

5. Server Requirement

ITEM NAME
OS Ubuntu 22.04
RAM 4 GB
Processor 2 GHz
Hard Disk 100 GB

6. Technology Stack

STACK USAGE
Language Backend NodeJS
Frontend ReactJS
Database MYSQL 8

7. Team Structure

Sr.No Skills No of Team

1 Frontend developer 1
 2 Backend Developer 1
3 Project Manager 1
4 QA 1

HIGH-LEVEL RELEASE PLAN

Weeks Deliveries

4 • Requirement Gathering
• APIs Development
• Frontend & Backend Development

TERMS AND CONDITIONS

⚫ 50% advance.
⚫ 50% on UAT sign-off.
⚫ Product support and training will start from go live date for 6 months
⚫ Any requirement from out of scope will charge extra.
⚫ Taxes excluded.
⚫ UAT and Production environment will be provided by the customer.
⚫ AMC will be as per Pay As You Go Model INR1200/Hr