The decision depends on your core business goals. Mobile app development covers a broad range of functionalities, news apps, booking systems, social platforms, while eCommerce app development is focused on online selling, product catalogs, payments, and order tracking. If sales and shopping experience are your priorities, go eCommerce-specific. For broader engagement or non-retail functions, a general mobile app may be better.

Choosing the right development partner ensures scalability, performance, and integration with your existing systems.

I’m currently hardening my Odoo production environment and want to ensure robust Odoo security. I’ve read about using an Odoo security scan to identify vulnerabilities but am unsure about the best tools or scripts to run. Should I focus on server-level hardening, Odoo configuration tweaks, or third-party security modules first?

Would appreciate guidance from anyone who has a tested checklist or automated approach for scanning and improving Odoo security in production.

I'm exploring ways to build a native mobile app that integrates seamlessly with a Laravel-based eCommerce platform, particularly Bagisto. I'm interested in best practices for exposing APIs securely, managing user sessions across devices, and syncing real-time inventory and cart updates.

Has anyone here used Webkul’s Laravel mobile app builder for Bagisto? I’ve seen they offer both Android and iOS native apps. Curious about the performance, API coverage, and whether it's customizable enough for multi-vendor marketplaces.

Any insights, tech stack suggestions, or success stories are welcome, especially around handling offline mode, push notifications, and integrating payment gateways natively.

Thanks in advance!

Sure! Here are the core Odoo implementation steps most teams follow:
Step 1: Business Process Review – Understand current workflows and identify bottlenecks.
Step 2: Module Selection – Choose only the modules relevant to your business (like Sales, Inventory, HR).
Step 3: Data Migration Planning – Define which legacy data needs to be migrated.
Step 4: Custom Development (if needed) – Customize features that are not available out-of-the-box.
Step 5: System Configuration – Set user roles, rules, and workflows.
Step 6: Testing – Perform functional and user testing.
Step 7: Training – Train staff on how to use the system efficiently.
Step 8: Go-Live & Support – Launch the system and provide support for any issues post-deployment.

Hi everyone,

If you're looking to implement a custom payment provider, such as Cash on Delivery (COD), and want it to be seamlessly confirmed through the Odoo website payment transaction flow, here's a quick breakdown based on our experience at Webkul.

Odoo lets you define new payment acquirers via the payment.acquirer model. For COD, you'd typically:
Create a new acquirer (e.g., payment_cod) with minimal API dependency.

Set state as 'enabled' and pre_msg/post_msg to inform customers about the payment terms.
Use the controller /payment/transaction to confirm the order post-checkout.

Ensure your payment.transaction record is updated correctly with state='done' or state='authorized' upon completion.
This method ensures that Cash on Delivery shows as a valid Odoo payment method on the checkout page and works with the core transaction confirmation logic.

Let me know if you're using a custom flow or want to integrate with a third-party gateway, Webkul has built various Odoo payment gateways and can share insights based on your use case.

Visit us at- https://store.webkul.com/Odoo/Payment.html

Looking to grow beyond basic online selling- Open source eCommerce platforms like Bagisto, WooCommerce, and PrestaShop offer serious flexibility without licensing costs. But with that freedom comes complexity. How are others here managing scaling, particularly with multi-vendor setups or custom marketplace features?

I’m curious about your experience with:

• Performance optimization for large catalogs

• Managing extensions and security patches

• Choosing between Laravel-based vs. PHP/Node-based platforms

• Real-world pros and cons of going fully open source

Would love to hear what’s worked (or not) for your marketplace.

Odoo provides a flexible way to manage various payment gateways, including PayPal, Stripe, and Razorpay, directly from its backend. By navigating to Invoicing > Configuration > Payment Acquirers, you can activate, configure, and test gateways based on your business needs. With Webkul’s support, you can extend its native capabilities to integrate region-specific Odoo payment methods, automate payment workflows, and deliver a seamless experience across eCommerce and POS systems.

Odoo Security plays a vital role in maintaining consistent and reliable business records. By configuring user access rights, role-based permissions, and record-level controls, teams can manage operations with precision and accountability.

Features like audit logging, encrypted connections, and group-based roles allow for structured data flow and organized workflows. These practices help reduce errors and keep operational data consistent across departments.

Adopting well-structured Odoo security practices supports smoother processes and dependable data across your entire system.

Hey Odoo Community,

I recently came across a few bugs and UI inconsistencies on the Odoo support page (odoo.com/help), and I’m wondering what’s the most effective way to report them? Is there a formal process for submitting feedback or issues directly to Odoo?

In our experience at Webkul, while working on Odoo Maintenance Services and providing long-term Odoo Support, we've seen how crucial timely feedback and bug tracking can be, not just for the core product but also for support usability.

Has anyone here had success getting a bug acknowledged or fixed by reporting it via the forum or email?

Also, would be helpful if Odoo had a dedicated GitHub tracker or community bug submission tool for these pages.

Looking forward to your thoughts!

Hi all,

I’m currently exploring ways to integrate our website with Salesforce Marketing Cloud and was hoping to get some clarity from those who’ve done it before. Our goal is to sync website activity (like form submissions, newsletter signups, and behavioral tracking) directly with Marketing Cloud to trigger automated journeys and personalize customer experiences.
Some questions I have:

What are the recommended methods or tools for website-to-SFMC integration?
Have you used API, JavaScript SDK (Web Collect), or CloudPages for capturing leads?
Any tips for Data Extensions, Contact Builder, or Journey Builder sync?
What challenges should we watch out for during implementation?

Also, if you’ve used Salesforce integration marketing cloud services or worked with a third-party tool, I’d love to know which ones you found effective and secure.
Appreciate any insights from developers, marketers, or Salesforce partners who’ve done this successfully!

Thanks in advance.