A project is a client-specific "bucket" for holding orders. It is an open-ended module that is not strictly defined because it can be used for any number of things. For example:
- A software company might use a project to represent an annual service contract or support agreement. Many orders for the same client can fall under the project, all pertaining to the same service contract.
- A magazine company might use projects to track magazine advertisers where each project is a contract for a specified number of ads.
- A service company might use projects to track retainers paid by their clients.
Your specific workflows will determine the best use of the Projects module.
Orders are records that record sales. They generate revenue and accumulate costs. Management can view them with granularity for transaction-level budgeting and profitability analysis. The level of information and the tools available to users in the Orders module is controlled by access privileges.
Jobs serve as the tracking mechanism for an order's budget, costs, fulfillment and related procurement.
Task are simply to-dos for users. They can be attached to any record in the system and can be created on the fly or they can be automatically created based on pre-defined templates. Time can be applied against tasks for granular time tracking and reporting.
The Shipping Log module tracks all shipments coming into and going out of your facility. Shipments are attached to purchase orders as part of procurement tracking and they are attached to orders and as part of fulfillment tracking.