# A few questions regarding modules

**URL:** <https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022>\
**Category:** English forums\
**Tags:** modules\
**Created:** [February 2, 2015, 3:42pm UTC](https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022 "2015-02-02T15:42:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![slax0r](https://forum.oxid-esales.com/letter_avatar_proxy/v4/letter/s/ea666f/32.png) [@slax0r](https://forum.oxid-esales.com/u/slax0r)\
**Post date:** [February 2, 2015, 3:42pm UTC](https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022/1 "2015-02-02T15:42:02Z")

</div>

Hello,

I have a few questions regarding the OXID module system. Obviously, because I’m posting here. 😉

Down to business, I have been tasked to develop a few modules for OXID to integrate with our backend system. Those modules will communicate through a REST API with our backend. The modules will consist of:

- user module (registrations, logins, profile/address(es),…)
- article module (article data import/export, storage quantity updates,…)
- cart module (CRUD over REST API basically)
- delivery module (payment/shipping options for an order,…)
- payment module (payment authorization and confirmation,…)

Plus possibly a few more, but those would be the start. Now my questions:

- is it possible to handle all user operations through modules, so the users would effectively register and login through the REST API? I don’t want duplicated user data on OXID and our backend system.
- is it possible to override from where OXID loads the article data(DB) and rather load it from the REST API?
- this one should probably work, as I still want to keep the cart in the users session, for quicker operations, but non-the-less, is it possible to integrate REST API calls for Cart CRUD?
- is it possible to load payment/shipping options from a REST API instead of the DB?
- I would much rather not keep any order data in OXID, but send everything over to the REST API, is it possible?

I really don’t want to duplicate data between two systems, because this can lead to hellish situations as it has in the past already. But the company wants a few modules that OXID users can simply install and connect with our backend(after making a contract with us of course).

And lastly, where can I find some nice documentation for writing modules on OXID?

Thank you in advance, and kind regards,  
Thomas

---

<div class="post-metadata">

**Author:** ![vanilla\_thunder](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/vanilla_thunder/32/72_2.png) [@vanilla\_thunder](https://forum.oxid-esales.com/u/vanilla_thunder)\
**Post date:** [February 2, 2015, 3:53pm UTC](https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022/2 "2015-02-02T15:53:22Z")

</div>

- yes
- it is possible, although you cant achieve that with modules and it will take big amount of time to get that working, because OXID uses a lot of hard coded sql queries.
- yes
- yes
- yes

but… in conclusion you want to cut off all ecommerce functions from oxid and let the frontend communicate with your own backend. Why?  
Why dont you develop a fancy (nodejs?) frontend for your backend instead of misusing an ecommerce software? i don’t think you and your boss will be happy with getting oxid work that way.

---

<div class="post-metadata">

**Author:** ![slax0r](https://forum.oxid-esales.com/letter_avatar_proxy/v4/letter/s/ea666f/32.png) [@slax0r](https://forum.oxid-esales.com/u/slax0r)\
**Post date:** [February 2, 2015, 4:03pm UTC](https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022/3 "2015-02-02T16:03:38Z")

</div>

Well, I kinda don’t want to change core files. Don’t want to put myself into a situation where I need to do more work when upgrading.

And we already have a ecommerce frontend for our backend, although not written in nodejs, as part of a different project, but it could quickly be cloned into a standalone probject, if need be. No idea why we don’t go that way for this client. Will definitely keep that in mind for the next meeting.

Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://forum.oxid-esales.com/user_avatar/forum.oxid-esales.com/system/32/4245_2.png) [@system](https://forum.oxid-esales.com/u/system)\
**Post date:** [July 13, 2026, 7:40pm UTC](https://forum.oxid-esales.com/t/a-few-questions-regarding-modules/72022/4 "2026-07-13T19:40:42Z")

</div>


