EKIKA Documentation

What are you looking for?

To keep things simple, choose the option that best matches you. We'll guide you to the most relevant topics.

How this documentation is organised

To keep things predictable, we group all articles into a few main areas:

• Odoo - everything related to Odoo implementations, customization, apps and hosting.
• CodeCanyon / Flutter + Laravel products - setup, updates and troubleshooting for our ready-made solutions.
• Shopify & E-commerce - patterns we use for real stores and multi-channel setups.
• Integrations & automation - n8n flows, APIs, webhooks and cross-system designs.
• Working with EKIKA - engagement models, communication rules, AMS / support, and partner guidelines.

Most pages will clearly show which area they belong to at the top, so you always know the context.

Types of articles you'll find here

We write different kinds of documents for different needs:

• How-to guides
  Step-by-step instructions for common tasks.
  Example: "Restore an Odoo backup to a new server".
• Concepts & decisions
  Short explanations of how we think about a topic and which options we usually pick.
  Example: "When we recommend Odoo.sh vs self-hosting".
• Checklists & templates
  Things you can literally tick or copy into your own documents.
  Example: "Pre-implementation checklist for a new Odoo project".
• Reference & API notes
  More detailed, sometimes technical information for engineers.
  Example: "Authentication flow for EKIKA API Framework".
• Release notes & known issues
  What changed in a product or module, and anything important you should be aware of before updating.

You'll see the article type near the title so you can quickly judge if it's what you need.

Status & versions

Our work touches multiple versions of Odoo, mobile apps and backends. To avoid confusion:

• Every article shows which versions it applies to.
  Example: "Applies to: Odoo 16, 17, 18 Community & Enterprise".
• When behaviour changes between versions, we either:
  • Split the article into separate version sections, or
  • Clearly highlight the differences in a "Version notes" block.
• If you are not sure whether something still applies to your setup, please:
  • Check the "Last updated" date at the top, and
  • Contact us if your environment is newer and not mentioned yet.

For EKIKA customers & partners

If you already work with EKIKA, this documentation is designed to:

• Give you clarity on our process (so there are fewer surprises).
• Help your team handle simple tasks without waiting for us.
• Make it easier to discuss changes with a shared vocabulary.

However, documentation does not replace:

• Your support / AMS contract,
• Incident handling for production issues, or
• Formal project scope / SOW documents.

When in doubt, always follow:

• Your signed agreement or SOW, then
• The latest relevant knowledge base article, and
• Your usual EKIKA contact / ticket system.

For EKIKA team members

If you are part of EKIKA, this site is also your working handbook:

• Use it to keep your answers consistent across projects.
• When you solve a problem more than once, turn it into an article.
• When something here is outdated or incomplete, note it and request an update instead of teaching a different pattern privately.

Our internal delivery playbooks, coding standards and confidential project details live in internal sections behind login. Public docs should never include:

• Customer names or private data without explicit permission,
• Screenshots of real production data,
• Access details, passwords or security-sensitive information.

Feedback & improvements

This documentation is never "finished". We improve it whenever:

• A customer asks a question that should be answered here,
• An engineer finds a clearer way to explain something, or
• A process changes and the old article is no longer correct.

If you notice anything:

• Unclear,
• Missing, or
• Wrong,

Please use the "Suggest an edit" or feedback link on the page, or mention it when you talk to us. Even a one-line note like "Step 3 is different in Odoo 18" is very helpful.

If you can't find what you need

Sometimes the right article doesn't exist yet.

If you are a customer or partner,

Please contact support or your EKIKA project owner. We'll help you directly and, where useful, create a new article based on your case.

If you are just exploring EKIKA,

Feel free to reach out through the contact form with your question. We prefer real, thoughtful questions over generic contact messages, and we try to answer with useful information first, not just a sales pitch.