Project Statement For Odoo Implementation
Project Statement For Odoo Implementation
03 3/13/2018
EJAM, INC.
This document and any communications with EJAM should be considered highly confidential. Neither the ideas
expressed herein, nor any part of this document or any other information or communications related thereto shall be
copied or disclosed to any party, nor shall they be used for any purpose other than meeting with representatives from
EJAM, without the written consent of EJAM. By accepting delivery of this document, the recipient agrees that:
I. in the event the recipient does not wish to pursue this matter, the recipient will return this copy to EJAM
II. the recipient will not copy, fax, reproduce or distribute this document, in whole or in part, without written
permission
III. all of the information contained herein will be treated as confidential material, and shall not be used for any
purposes other than evaluation.
EJAM, INC.
Email: [email protected]
1.0 Objective
EJAM is seeking development assistance to migrate its business’ core operation from various platforms to a unified
platform where the system is easy to expand and development resource is wider.
EJAM wishes to improve on: 3PL (3rd Party Logistic) warehouse integration (Rakuten, Amazon FBA) on inventory
levels, dispatches, & fulfillment; unified sales system by incorporating Customer Relation Management (CRM)
system; HelpDesk for customer service; basic accounting configuration; better inventory forecast between
procurement and 3PL (3rd Party Logistic) warehouses; user-friendly dashboard interface
● SendGrid
● ChatFuel-
● Konnektive- Is the CRM- This is where products need to get created before deployment
on dashboard.
The ideal new system(s) will provide easy-to-use interface that limits user-training to the lowest possible; seamless
communications between team members, great reporting data for department managers, accounting report functions,
purchase and multiple 3PL warehouse management, inventory forecast and projection, 3PL shipping rate
integrations, easier order confirmation process with customers, and ability to have orders created in Odoo by
offering custom landing page to process credit card payments.
● 3PL inventory, dispatch order, shipment rate & tracking update, inventory transfer via API or EDI
(Rakuten)
● 3PL inventory, dispatch order, shipment rate & tracking update, inventory transfer via API or EDI (Rapid
Fulfillment)
● 3PL inventory, dispatch order, shipment rate & tracking update, inventory transfer via flat file such as CSV
(Lansil)
● Partial/declined campaign generation for post-sale and abandon-cart operation
● 3rd Party Email marketing system integration
● Chargeback data import (Paypal Vantiv – WorldPay, Ebanx, Seezzle))
● Landing Page / Checkout Page javascript import via API
● Calculation of product margin & net costs
● Inventory forecasting ability
● Credit card transaction settlement automation through Paypal, WorldPay (Vantiv)
● Electronic bank reconciliation
● Automated emails for order confirmation & tracking update
● Trackable links for tracking numbers (USPS, UPS, FedEx, DHL) in Odoo and emails
1.1 Baseline
This document presents the Project Statement for the implementation and customization of Odoo ERP and
represents an overview of EJAM’s requirements for this project.
1.2 Revision
You may request a revision to the Project Statement with knowledge that such revision may impact the scope and
timing of this Project Statement.
EJAM is looking for a system to unify the platforms that it’s currently using:
● Order management
● Fulfillment management with 3rd-party warehouses
● Inventory management with 3rd-party warehouses
● Helpdesk support tickets
● Purchasing document management
● Purchasing new product campaign management
● Accounting & tax reporting
● Sales
● Inventory
● CRM
● Purchase
● Invoicing
● Discuss
● Calendar
Default Module Setup & Configurations Commented [2R1]: Default Odoo Purchase Analysis
module example:
https://screencast.com/t/YhKgXot9
SALES
If we create views, the charges are minimum; if
creating a report that the Purchase Analysis does not
Enable the following settings: support, then the charge is higher (ex, Dashboard
reports)
Product Packagings, Discounts, Multiple Sales Prices Per Product (Multiple prices per product (e.g.
customer segments, currencies)), Margins, Customer Account (On invitation), Customer Addresses,
Shipping Costs, Delivery Date, Order-Specific Routes, Invoice what is delivered
Customer Attributes:
● Invoiced
● Partial (abandon cart, customer filled in partial contact information)
● Declined (credit card declined)
● Refunded (credit memo is created)
● Cancelled (Sales Order is cancelled and order is never fulfilled)
INVENTORY
Warehouse details:
https://docs.google.com/spreadsheets/d/1h85_x_2u-9Pj9wqHR9iJL6nXn_fyZghtiJ-
xRiX9Ua4/edit?usp=sharing
Inventory Tracking:
● Total Inventory Qty divided by Daily Sales Velocity (Average sales of last 7 days) = # of days
left in inventory
● “Total Inventory Qty divided by Daily Sales Velocity (Average sales of last 7 days) = # of
days left in inventory)” - Factory Lead Time + Shipping Lead Time = Days we need to
reorder
● EX: Wash Wizard: Total inventory: 5551/283 = 19.6 Days until out of Inventory
● Ex: 19.62 - (12 Days Factory Lead Time + 10 Days Air Freight) = -4 (Days Until Reorder
(Airfreight))
● Ex: 19.62 - (12 Days Factory Lead Time + 10 Days Air Freight) = -4 (Days Until Reorder
(Fast Boat))
Example
Stage Filters:
● Brand
● Shops
● Country (use shipping address country first; if not available, use bill-to address country)
Lost Reasons:
● DC – Disconnected Numbers
● DNC – Do Not Call
● NA – Not Available
● NI – Not Interested
PURCHASE
Enable the following settings: Commented [9]: When the time comes to implement
this, make sure that we discuss how deposit payments
will be posted against the balance sheet to avoid
● Purchase Order Approval, Bill Control (Delivered quantities)
inventory paid but not received situations like we had in
previous companies
Purchase order workflow:
Commented [10R9]: This should be a controllable
user process to always pay the remaining balance only
● Request for Quotation after shipment is ready to go out and booking of
● Email vendor PQ in PDF container has scheduled.
● Vendor confirmation
● Odoo user uploads vendor Performa Invoice We can also add a system validation process to require
Odoo user to click a button or update BOL numbers to
● Confirm PQ (Purchase Quote) to create PO (Purchase Order) validate shipment before final payment can be made by
● Managers Validates PO accounting.
● Send PO to vendor
● Odoo user uploads vendor invoices
● Odoo user creates Bill for initial deposit
● Odoo user notifies accounting department for remaining balance
● Accounting Validates Bill in Odoo
● Accounting Register Payment in Odoo
● Accounting Validates payment
● Odoo users adds Landed Cost (freight charge) to PO
● Odoo user confirms inventory receipt in Odoo
● https://drive.google.com/file/d/1zrRqWEitGQ-
DCw6OoztdYoqbrURMKOn3/view?usp=sharing
INVOICING
Chart of Accounts:
● USD
● EUR
● Install Currency Converter App for daily exchange rate update:
https://www.odoo.com/apps/modules/12.0/xe_currency_converter/
Tax:
● Taxes are used only when the state of customer’s shipping address is the same as the ship-from
warehouse’s state Commented [11]: This is an incorrect statement, and
● Import taxes for states where warehouses are located in the U.S. needs to be updated with 2019 tax laws
● Connect to an external platform to download sales tax rates
Commented [12R11]: TaxJar is an app that provides
o Import sales tax (based on counties level) via API (once a day, overwrite) via TaxJar
realtime tax rates by counties. This project is to
connector connect to an external platform to download sales tax
o Reference module: rates
https://github.com/LasLabs/odoo-connector-taxjar
Bank Accounts:
Payment Acquirers:
CALENDAR
NOTES
TIMESHEETS
Workflow: https://drive.google.com/open?id=1afV6F5kbE1mzjpGxaTpwlCL2eHc2pBzD Commented [20]: This is sufficient for the current set
up, but how will we integrate via API, EDI, or CSV
upload for clients other than the ones contemplated on
Requirements: this list?
Commented [21R20]: The system has framework to
support all three types of data feed that you mentioned;
● New order data are separated into the following types: the GoogleSheet for 3rd-party modules includes
o Shopify installation for CSV/API imports. Additionally Odoo
o Landing Pages (EJAM Dashboard) supports EDI; developer will just need to make
templates matching client's EDI templates.
o Phone Orders (entered manually by Odoo users)
Commented [22]: Does the system support line item
o Amazon (FBA)
level for film it from different physical locations? If so
● Product location: has that and contemplated in this implementation?
o Rakuten Commented [23R22]: I am not sure I understand your
question; can you give me more information?
● Upon checkout, when submitting payment, if credit card is selected as payment type,
payment data is sent from EJAM Dashboard (a Heroku Platform) via API to Odoo and
use Emipro Odoo WorldPay Payment Acquirer module to collect payment
o The payment status (ex, Authorized, Captured, Authorized & Captured,
Declined) needs to create respond in API
o Odoo Sales Order Number and Invoice Number needs to be responded in API as
well
● Upon checkout, when submitting payment, if Paypal is selected as payment type,
payment data is sent via API to Odoo and use Forfens Tech’s PayPal Payflow Pro
Payment Gateway app to collect payment
Custom Rakuten Shipping Charge Reports Commented [24]: Are we currently passing live rates
through the shopping cart, or do we work off of a
weight-based chart for our estimated charges?
Purpose: Compare the price that Rakuten charges us against the estimated shipping charges based on
agreed charges from Rakuten’s invoice I would like to see how this works. In the past I have
created a custom fields and have been able to pull into
each sales order and do a cash sale line item cost from
Integration: a three PL for reconciliation purposes.
Commented [25R24]: We do not passing live rates;
● Use “Shipping Charge” from Rakuten’s API feed we currently offer free-shipping on all products
● Actual Shipping Charge = Handling Charges (from Correct, this requires creating fields called "Expected
https://drive.google.com/file/d/1Qn6wfgHKhAqmBK_5KW0EpWOuXWAK8uR4/view?usp=shar Shipping Charge" and "Actual Shipping Charge" for
sales orders, then the reconciliation can be at per
ing) + Discount
transaction level.
● Handling Charge = Projected number of packages based on average packages per day for the
current month;
o ex, if projected monthly packages shipped by Rakuten Warehouse in Odoo is 5001, the
handling charge per box is $1.17 per package (shipping box)
Customization:
● https://docs.google.com/spreadsheets/d/1hEiuNK4w_g23OL-
iFWzhzwR0b3qscnx4rL_FXuyVu_U/edit?usp=sharing
● Report should include export in PDF and Excel (CSV)
● https://docs.google.com/spreadsheets/d/14aUB_6SZUD9V3PkdWW6r6hfpcamjjEGs9oPaYswP70k/edit?us
p=sharing
● Developer will move any added files in the upgrade, make sure core modification to any JS or prototype
files will not be overwritten on upgrade.
● EJAM will provide a list of these files in advance.
● Developer understands that all third party modules, along with any local overrides, must be tested.
● EJAM will be responsible for the purchase of any modules that need to be acquired unless otherwise
specified by EJAM.
● Developer will test the functionality of site using the default theme. The tests will include the following:
access to the admin panel, functioning crons.
● Developer will receive full access to the decided upon hosting environment. This includes: root access to
the server via SSH, and access to and credentials for other relevant services such as PostgresSQL and
SFTP/SCP .
● Developer will notify EJAM prior to any downtime on the live site.
● Developer will offer testing to EJAM at critical junctures to ensure proper UAT.
7.0 Signatures
COMPANY NAME
_____________________________________________________ __________________
Authorized Signature Date
Signatures in the boxes above indicated acceptance the original Project Statement as described. Authorized
signatures are those from individuals with the rights to sign contracts on behalf of their organizations. Any changes
to the original document must be made through the Change Order Management System.