Moving from PrestaShop to Oscar

[Alper Kanat]

Hey There,

I'm currently weighting my options for a transition from PHP to Python while considering writing from scratch or using django-oscar. I know that Oscar has lots of features that would save our time reimplementing but I can't make sure Oscar works for us without much of a hassle.

We sell shoes, handbags and other stuff so we have the following use case:

• We have a product with an ID (say 1881) which has some combinations.
• Each combination is associated with a unique barcode number and stock information. (stock seems to be tied to Partners in Oscar) So if product has 5 combinations (EU sizes 35, 36...) and each of them has 100 products available, then 1881's available stock is actually 500.

I can't figure out how to achieve this with Oscar. Any ideas?

Besides this I'd like to use attributes (size, colour, material, origin etc..) for filtering. However since an attribute may have different values, I also can't figure out how to achieve this.

There are also lots of missing parts in the docs with broken links:

• It doesn't cover django.contrib.admin requirement for managing product classes and other stuff.
• South fixture doesn't come with a predefined admin account so had to give necessary privileges for admin and dashboard via python shell (or db). This is not covered in the docs as well.
• Sandbox was broken throughout the day. It now works.
• "The sandbox site can be set-up locally in 5 commands. Want to make changes? Check out the contributing guidelines." -- Contributing Guidelines (aka [1] is broken).
• Many of the things that can be seen in /admin/ are not covered in the docs. So one has to dig deeper in the code as there is not much information on Google available as well.

I really liked the dashboard and availability of mail alerts etc though. Thanks for the good work!

[1] http://django-oscar.readthedocs.org/en/latest/contributing/index.html

---
Quis custodiet ipsos custodes?

[Izidor Matušov]

Hey Alper,

you can use `make sandbox` command to setup sandbox site (including
admin user *superuser*.


Izidor Matušov
Developer

Tangent Snowball
84-86 Great Portland Street
London
W1W 7NR




www.tangentsnowball.com

Tangent Snowball is a registered trading name of Tangent Marketing Services Limited
Registered Office: 84-86 Great Portland Street, London W1W 7NR
Registered in England Wales Number 4323657

This message contains confidential information and is intended only for the individual named.
If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system.

[David Winterbottom]

On 3 September 2013 16:40, Alper Kanat <tu...@raptiye.org> wrote:

Hey There,

I'm currently weighting my options for a transition from PHP to Python while considering writing from scratch or using django-oscar. I know that Oscar has lots of features that would save our time reimplementing but I can't make sure Oscar works for us without much of a hassle.

We sell shoes, handbags and other stuff so we have the following use case:

• We have a product with an ID (say 1881) which has some combinations.
• Each combination is associated with a unique barcode number and stock information. (stock seems to be tied to Partners in Oscar) So if product has 5 combinations (EU sizes 35, 36...) and each of them has 100 products available, then 1881's available stock is actually 500.

I can't figure out how to achieve this with Oscar. Any ideas?

​Normally, each variation of a product has a different SKU.  This makes sense as the warehouse needs to track their stock levels individually.  

In Oscar, if you have a product available in 5 sizes, you would create 6 product instances: 1 parent version which contains all the shared details but has no stockrecord, and 5 variant, child instances which only contain the details/attributes that differ (eg the size).  Each variant would have its own stockrecord with a SKU, price and stock level.​

It's worth noting that Oscar's support for variant products still needs some attention.  The models underneath work well but the interface for creating/editing them is clunky.  I was hoping this would get some attention for v0.6 (due shortly) but that's not going to happen.  More likely 0.7 will feature better variant support.

 

Besides this I'd like to use attributes (size, colour, material, origin etc..) for filtering. However since an attribute may have different values, I also can't figure out how to achieve this.

There are also lots of missing parts in the docs with broken links:

• It doesn't cover django.contrib.admin requirement for managing product classes and other stuff.

​The docs have this section on creating product classes - is it unclear?​

 

• South fixture doesn't come with a predefined admin account so had to give necessary privileges for admin and dashboard via python shell (or db). This is not covered in the docs as well.

​I don't follow.  The sandbox comes with a sample superuser that is loaded via the makefile.  Are you talking about running the sandbox site locally, or about a fresh Oscar install?​

• Sandbox was broken throughout the day. It now works. 

• "The sandbox site can be set-up locally in 5 commands. Want to make changes? Check out the contributing guidelines." -- Contributing Guidelines (aka [1] is broken).

​Good spot - now fixed.​

• Many of the things that can be seen in /admin/ are not covered in the docs. So one has to dig deeper in the code as there is not much information on Google available as well.

​In general, Oscar isn't designed to use Django's admin suite.  We do ship some admin.py modules though so I can see how this is slightly confusing​.  I've created a ticket to go through the docs and make sure they are clear about the admin.

https://github.com/tangentlabs/django-oscar/issues/816

Thanks for these notes on getting started - they are very useful.

 

I really liked the dashboard and availability of mail alerts etc though. Thanks for the good work!

[1] http://django-oscar.readthedocs.org/en/latest/contributing/index.html

---
Quis custodiet ipsos custodes?

--
https://github.com/tangentlabs/django-oscar
http://django-oscar.readthedocs.org/en/latest/
https://twitter.com/django_oscar
---
You received this message because you are subscribed to the Google Groups "django-oscar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-oscar...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-oscar.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-oscar/CAPMuxnTbAg0PQQTFf9avjoM784hfU9bghZCKib-XX0M9y9YNqw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
David Winterbottom
Head of Programming

Tangent Labs

84-86 Great Portland Street
London W1W 7NR

England, UK

[Alper Kanat]

Hi David,

Thanks for the replies. We have different codes as barcodes while warehouse track them seperately in their own system. We use ean13 together with a reference barcode such as 10001-10341 or 19244-35 which represents shoe size 35 for a given shoe. I'm not using the sandbox btw. I just installed a virtualenv and installed oscar via pip, created a django project and included oscar in it.