Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
Lines of code | 609 |
Technical Name |
foodics_account |
License | OPL-1 |
Website | https://www.digizilla.net |
Versions | 17.0 |
Foodics Integration
Foodics & Odoo Integration
The integration connects Foodics with Odoo, enabling automatic synchronization of sales transactions, inventory updates, and customer data. This ensures real-time data consistency between both platforms, streamlining operations and reducing manual entry across your business processes.

Account Setup
Create a Foodics account and select either the test or production environment. You can also choose a read-only mode if the data should not be editable. Then, enter your Foodics POS API credentials to activate the integration.

Settings Tab Configuration
Easily configure how the integration behaves by setting the following options:
Customer & Journal Setup
Define the default customer and accounting journal to be used for incoming Foodics orders.

Customer Handling
Choose how customer data from Foodics is managed in Odoo:
- Unify Customer: All orders from Foodics are assigned to a single customer defined in the settings.
- Handle Separately: Orders are linked to individual customers as received from Foodics.

Linking Type
Decide how Foodics orders are represented in Odoo:
- Create Sales Orders
- Create Invoices

Order Status
Select the default state for created records:
- Draft or Confirmed Sales Orders
- Draft or Confirmed Invoices
This can be controlled through a status field in the settings.

Automatic Daily Linking
Fetch and sync Foodics orders automatically each day using a scheduled action, or manually link them whenever needed.

Pull Data Tab
In the Pull Data tab, you'll find toggle switches for syncing data from Foodics to Odoo â such as branches, orders, categories, and more.
- When enabled: Data is fetched automatically.
- When disabled: You can still fetch the data manually using the provided action buttons.

Fetched Data Management
Fetched data is organized and accessible in its corresponding menu within Odoo. For example, if you choose to fetch Foodics orders, they will appear under the Foodics Orders menu, etc.

Branch Configuration
Once branches are fetched from Foodics, they can be accessed from the Foodics Branches menu under the Configuration tab. For each branch, you can:
- Link it to a corresponding warehouse source location
- Assign an operation type
- Add an analytics account

Payment Methods Configuration
After fetching payment methods from Foodics, you can assign an appropriate journal to each method directly in Odoo.
This ensures that all incoming payments are accurately recorded in the correct financial accounts, allowing seamless integration with your accounting workflows.

Contact Information
3 Makram Ebeid, City Center Building, Nasr CityPhone: +201061586539
Email: bd@digizilla.net
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module