blocks|key|1496824|text|我对Django一无所知，但几年前，我们公司决定停止将它用于销售，并用PHP开发自己的解决方案后，我也遇到了同样的问题。我们与共享(+shopify，虽然我从未使用过)这样的托管平台的问题是，他们的费用比你只需要滚动自己的解决方案和处理您的订单与贝宝或其他东西要高得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1496825|所以你可以考虑做我们做的事情:购买预先构建的购物车软件，然后广泛定制它。我们使用了Digishop，它更多地是为在线目录类型的商店设计的，而不是我们的软件站点，但是经过大约2-4周的添加必要的功能，这是很好的选择。尽管开箱即用的Digishop对于我们的需求来说太臃肿了，但是如果您熟悉PHP，那么浏览它并根据您的需要有选择地添加或删除特性应该是一件轻而易举的事情。|offset|length|1496826|祝好运!|1496827|entityMap|0|LINK|mutability|MUTABLE|url|http://digishop.sumeffect.com/^0|0|15|8|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I don't know anything about Django, but I faced this exact same problem a few years ago after our company decided to stop using share-it for sales and develop our own solution in PHP. Our problem with hosted platforms like share-it (and I assume shopify, although I've never used it) is that their fees are much higher than you would incur by just rolling your own solution and processing your orders with Paypal or something.

So you may consider doing what we did: buying pre-built shopping cart software and then extensively customizing it. We used <a href="http://digishop.sumeffect.com/" rel="nofollow">Digishop</a>, which is designed more for a online catalog-type store than our software site, but after about 2-4 weeks of adding necessary functionality it was good to go. Although out of the box Digishop was way too bloated for our needs, if you're familiar with PHP it should be a breeze to navigate through it and selectively add or remove features as you see fit.

Good luck!

blocks|key|2693332|text|您可以尝试两种DJango电子商务解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2693333|闪电快餐店+(演示)|unordered-list-item|offset|length|2693334|萨奇莫+(演示)|2693335|就PHP而言，我们使用了osCommerce+(演示)。|2693336|entityMap|0|LINK|mutability|MUTABLE|url|http://www.getlfs.com/|1|http://demo.getlfs.com/|2|http://www.satchmoproject.com/|3|http://demo.satchmoproject.com/|4|http://www.oscommerce.com/|5|http://www.oscommerce.com/shops/demonstration^0|0|0|5|0|7|2|1|0|0|3|2|5|2|3|0|C|A|4|O|2|5|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@$E|14|F|15|1|16]|$E|17|F|18|1|19]]|A|$]]|$1|G|3|H|5|D|7|1A|8|@]|9|@$E|1B|F|1C|1|1D]|$E|1E|F|1F|1|1G]]|A|$]]|$1|I|3|J|5|6|7|1H|8|@]|9|@$E|1I|F|1J|1|1K]|$E|1L|F|1M|1|1N]]|A|$]]|$1|K|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]|W|$5|N|O|P|A|$Q|X]]|Y|$5|N|O|P|A|$Q|Z]]|10|$5|N|O|P|A|$Q|11]]]]

Two DJango e-commerce solutions you might try:

<ul>
<li><a href="http://www.getlfs.com/" rel="noreferrer">Lightning Fast Shop</a> (<a href="http://demo.getlfs.com/" rel="noreferrer">demo</a>)</li>
<li><a href="http://www.satchmoproject.com/" rel="noreferrer">Satchmo</a> (<a href="http://demo.satchmoproject.com/" rel="noreferrer">demo</a>)</li>
</ul>

As far as PHP goes, we've used <a href="http://www.oscommerce.com/" rel="noreferrer">osCommerce</a> (<a href="http://www.oscommerce.com/shops/demonstration" rel="noreferrer">demo</a>).

blocks|key|3051409|text|我对Django没有经验。我使用Wordpress开发网站，一年前我测试了Magento+(从那以后就没有测试过)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3051410|我对Magento的用户友好感到惊讶。前端和后端都是。建立起来真的很容易。您也可以使用Magento模板API轻松地自定义布局。|3051411|以下是一些利弊：|3051412|Pros|offset|length|style|BOLD|3051413|不要开发自己的电子商务网站。要重新发明轮子还有很多工作要做。|unordered-list-item|3051414|通过使用知名的电子商务产品，您也会得到支持。|3051415|像Magento这样的电子商务平台很容易建立，并且提供了改变外观和感觉的选项，以与网站的其他部分相匹配。|3051416|您可以轻松地将CMS和电子商务结合起来。|3051417|像Magento这样的电子商务平台提供自定义静态/动态页面的选项(就像一个迷你cms)。|3051418|通过使用已经开发的东西，您将节省资金(开发时间)。|3051419|大多数电子商务网站都负责向不同的银行提供商付款。|3051420|Cons|3051421|Magento不适用于所有服务器(服务器配置)。然而，这种情况在过去一年中可能发生了变化。|3051422|如果像Magento这样的免费电子商务产品不能满足您的需求，您需要购买许可证。这要花很多钱。|3051423|如果你想要质量和可用性的话，开发自己的电子商务网站需要花费大量的时间。你不可能在3个月内从零开始开发一个好的电子商务网站。|3051424|entityMap^0|0|0|0|0|4|0|0|0|0|0|0|0|0|0|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1D|8|@$H|1E|I|1F|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|N|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|N|7|1I|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|N|7|1K|8|@]|9|@]|A|$]]|$1|W|3|X|5|N|7|1L|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|N|7|1M|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1N|8|@$H|1O|I|1P|J|K]]|9|@]|A|$]]|$1|12|3|13|5|N|7|1Q|8|@]|9|@]|A|$]]|$1|14|3|15|5|N|7|1R|8|@]|9|@]|A|$]]|$1|16|3|17|5|N|7|1S|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|19|$]]

I've no experience with Django. I develop websites using Wordpress and a year ago I tested Magento (not tested it since).

I was surprised of how user friendly Magento was. Both front end and backend. It was really easy to set up. You can easily customize the layout as well using Magento template API.

Here are some pros and cons:

Pros 

<ul>
<li>Don't develop your own e-commerce site. It's a lot of work to re-invent the wheel.</li>
<li>By using a well know e-commerce product, you will also find support.</li>
<li>E-commerce platforms like Magento are easy to set up and offer the option of changing the look and feel to match the rest of the web site.</li>
<li>You can easily combine CMS and e-commerce</li>
<li>E-commerce platforms like Magento offer the option for custom static / dynamic pages (like a mini cms)</li>
<li>You will save money (development time) by using something that is already developed</li>
<li>Most e-commerce sites handle payment towards different banking providers.</li>
</ul>

Cons 

<ul>
<li>Magento does not work on all servers (server configuration). This however might have changed in the past year.</li>
<li>If free e-commerce products like Magento do not satisfy your needs, you need to buy licenses. And that costs a lot of money.</li>
<li>It takes a lot of time developing your own e-commerce site if you want quality and usability. There is no way you can develop a good e-commerce site from scratch in just 3 months.</li>
</ul>

blocks|key|2693400|text|由于最后期限是3个月，你绝对应该使用一个现有的，打包电子商务。我相信我不会是唯一一个指出这一点的人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2693401|同样，你可能会发现，要想跟上Magento+--这是准企业--的复杂性，需要整整3个月的时间。作为一个妥协，您可能会发现Magento满足您的需要，从一些经验丰富的专业人士的外部帮助。(我是如此的专业，我喜欢Magento，因为它的复杂性和特点)|2693402|还有更多的电子商务解决方案可供选择，我不可能把它们都列在这里。也不要觉得与某一种语言有联系，将来你可能不是唯一一个修复这个网站的人，所以看看你的雇主可以获得的技能。Python的增长不如其他语言，例如PHP和Ruby，可能不会成为未来。|offset|length|2693403|entityMap|0|LINK|mutability|MUTABLE|url|http://redmonk.com/sogrady/2011/04/04/changes-programming-languages/^0|0|0|2A|F|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Since the deadline is 3 months you should definitely use an existing, packaged ecommerce. I'm sure I won't be the only to point that out. 
Equally, you might find it takes all of 3 months to get up to speed with Magento - which is quasi-enterprise-complexity. As a compromise you might find Magento suits your needs with a little outside help from some experienced professionals. (I am such a professional and I like Magento for it's sophistication and features)

There are many more ecommerce solutions out there to choose from, I couldn't possibly list them all here. Don't feel tied to a particular language either, you might not be the only one to fix the site in future so look at the skills available to your employer. <a href="http://redmonk.com/sogrady/2011/04/04/changes-programming-languages/" rel="nofollow">Python's growth doesn't compare well to other languages</a>, such as PHP and Ruby, so may not be the future.

blocks|key|1496957|text|在此之前，我们中的许多人都处于相同的情况--代码从无到有(CFS)或使用框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1496958|我的经验--我开始用Perl编写脚本。PERL最常用的模块之一(用于web编程)是CGI。一些人认为它是一个“沉重”模块，因此少数已经开发了“更轻”版本的它。对于新手来说，这可能会让人困惑--使用哪个模块？在浏览Perl的归档邮件列表时，我发现了我仍然认为是智慧之瑰宝的东西--您不知道的东西与您知道的一样重要。|offset|length|style|BOLD|1496959|这位perl大师提醒大家，CGI模块已经被许多开发人员审查过了。他接着解释了C处理字符串的方式(Perl是用C制作的)是如何被破解者用来利用web应用程序的，但是CGI模块有代码来防止这种安全漏洞。他接着补充说，他来的新CGI模块都没有代码来防止同样的漏洞，因为他们都没有意识到这个问题！|1496960|当然，就像詹姆斯·布莱克(+James+)对你的问题发表的评论一样，你也需要考虑时间因素。|1496961|在选择框架或模块时：|1496962|看看它有多老。|ordered-list-item|1496963|看看它的开发人员有多活跃(通过邮件列表归档、IRC等等)。|1496964|开发人员是否提供了良好的支持？|1496965|安全吗？|1496966|很受欢迎吗？|1496967|entityMap^0|0|3V|C|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|P|7|18|8|@]|9|@]|A|$]]|$1|S|3|T|5|P|7|19|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1A|8|@]|9|@]|A|$]]|$1|W|3|X|5|P|7|1B|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|Z|$]]

Many of us have been in the same situation before - code-from-scratch (CFS) or use a framework. 

My experience - I started scripting with Perl. And one of the most used module (for web programming) of PERL is CGI. Some considered it a 'heavy' module and thus a few had developed a 'lighter' version of it. For a newbie, this could be confusing - which module to use? Browsing the archive mailing lists of Perl, I came across what I still consider a gem of a wisdom - what you don't know matters as much as what you know. 

This perl guru reminded everyone that the CGI module had been reviewed by many developers. He went on to explain how the way strings was handled by C (Perl is made with C) was used by crackers to exploit web apps, but the CGI module had code to prevent such security exploits. He went on to add that NONE of the new CGI modules thats he had come aross had code to prevent this same exploit because none of them were aware about this issue!

And ofcourse, like James Black commented on your question, you need to consider the time factor too. 

When selecting a framework or module:

<ol>
<li>Look at how old it is.</li>
<li>Look at how active it's developers are (through mailing lists archives, IRC etc).</li>
<li>Do the developers provide good support?</li>
<li>Is it secure? </li>
<li>Is it popular?</li>
</ol>

blocks|key|2693498|text|在一天结束时，答案归结为你对这两种选择的合宜性。在过去，当我遇到这两个选项时，我通常会使用先前存在的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2693499|创建自己的理由：|2693500|Flexability+--您可以编写您想要的以及希望它如何工作的程序。|unordered-list-item|offset|length|style|BOLD|2693501|你知道代码。当一些东西坏了，你就知道你写了什么，希望不用看一大堆文档就能找到问题的根源。|2693502|使用开箱即用/开源解决方案的原因|2693503|社区--这对我来说是最大的。当你在寻求解决问题的帮助时，有一个社区在你身后可能是最大的帮助。很有可能有一个人已经遇到了问题，你正在努力做你想要完成的事情。|2693504|预先存在的API解决方案--如果您正在创建一个在线商店，您很可能需要绑定到某个API中进行结帐/发货。外面主要的购物车已经建好了。例如，Zencart有授权模块、Paypal模块、UPS模块、FEDEX模块、USPS模块。以及一些您可能需要与之交互的其他API。它将为您节省大量的时间，而不必为所有这些不同的服务编写API脚本。|2693505|Security+--这两者都可以。通过使用更熟悉的解决方案和自定义的解决方案，您将面临陷入儿童脚本黑客的风险，在这种情况下，人们使用脚本侵入特定类型的在线购物车。但是同时，如果有一个开发人员社区来解决安全问题，那么对安全漏洞的响应要比您试图单独解决它快得多。|2693506|Timeline+--启动开源商店比编写自己的商店要快得多。举个例子，如果你用Zencart。您可以安装商店，然后花费您的时间修改皮肤外观和功能，您希望。|2693507|我不得不投票赞成使用赞卡作为解决方案。我用了好几次，软件从来没有让我失望过。他们有一个很棒的社区，比现在感觉相当死气沉沉的oscommerce强得多。|2693508|此外，使用zencart，您可以制作静态页面，您可以在其中放置任何您想要的内容。当然，您也可以添加第二个CMS来处理静态页面。|2693509|entityMap|0|LINK|mutability|MUTABLE|url|http://www.zen-cart.com/^0|0|0|0|B|0|0|5|0|0|0|2|0|0|C|0|0|8|0|0|8|0|A|2|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@$G|1B|H|1C|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|1D|8|@$G|1E|H|1F|I|J]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1H|8|@$G|1I|H|1J|I|J]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1K|8|@$G|1L|H|1M|I|J]]|9|@]|A|$]]|$1|S|3|T|5|F|7|1N|8|@$G|1O|H|1P|I|J]]|9|@]|A|$]]|$1|U|3|V|5|F|7|1Q|8|@$G|1R|H|1S|I|J]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1T|8|@]|9|@$G|1U|H|1V|1|1W]]|A|$]]|$1|Y|3|Z|5|6|7|1X|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

At the end of the day, the answer comes down to how comfertable you are with both options. In the past when I have come across the 2 options, I usually go with the preexisting solution.

Reason to create your own:

<ul>
<li>Flexability - You can do program what you want and how you want it to work.</li>
<li>You know the code. When something break you know what you have written and hopefully can find the source of the problem without reading a bunch of documentation</li>
</ul>

Reason to use a out of the box/open source solution 

<ul>
<li>Community - This is the biggest for
me. When you are looking for help
with a problem, having a community
behind you can be the biggest help.
Chances are there is someone out
there that has had to problem you are
having/is trying to do what you are
trying to accomplish.</li>
<li>Preexisting API solutions - If you
are creating an online store, chances
are you are going to need to tie into
some API for checkout/shipping. The
major shopping carts out there have
these already built out. For
instance, Zencart has modules for
Authorize, Paypal, UPS, FEDEX, USPS.
As well as a bunch of other API that
you might need to interact with. It
will save you a ton a time not having
to code out API scripts for all of
these differnet services.</li>
<li>Security - This could go in both.
With using a more well know solution
vs a custom one, you run the risk of
falling into a kiddy scripting hack
where people use scripts to hack into
a specific type of online cart. But
at the same time, if there is a
community of developers solving
security issues then response to a
security breach would be much faster
than you trying to solve it alone.</li>
<li>Timeline - Launching a open source store is way faster then writing your own. If you used Zencart for example. you could install the store and then spend you time modifying the skin to look and function how you would like. </li>
</ul>

I'd have to put my vote in for using <a href="http://www.zen-cart.com/" rel="nofollow">Zencart</a> as a solution. I've used then on several occation and the software has never let me down. They have a great community, much more so than oscommerce which feels pretty dead at this point. 

Also with zencart you can make static pages where you can put whatever content you want on them. You could of course also put a second CMS to handle the static pages.

blocks|key|1497039|text|如果你在Magento/Satchmo和你更喜欢Django之间，一定要和Satch一起去。我使用过这两种方法，并且坦率地说，马根托是一场噩梦。+(如果这看起来是一段有趣的时间的话)。在我的经验中，Django/Satchmo更灵活、更易于定制、更易于维护，而且您还可以利用Django丰富的软件包生态系统。而且说真的Python+>+PHP。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1497040|从长远来看，我认为你和Django/Satchmo在一起会更好。在遥远的将来某个时候(因为没有一个项目是真正完成的，或者你最初的需求可能暗示的那样简单)，你的客户会回来说：“哦，well...we真的希望X在用户Y做Z的时候发生”。到那时，你要么说“没问题，你的网站是建在Django上的，所以这是小菜一碟！”或者进入抽搐，因为你会想到与马根托有关的所有工作。|1497041|entityMap|0|LINK|mutability|MUTABLE|url|http://www.magentocommerce.com/knowledge-base/entry/magento-for-dev-part-1-introduction-to-magento|1|http://djangopackages.com/^0|1R|9|0|3T|G|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you are leaning between Magento/Satchmo and you prefer Django, definitely go with Satch. I've worked with both and frankly <a href="http://www.magentocommerce.com/knowledge-base/entry/magento-for-dev-part-1-introduction-to-magento" rel="nofollow">Magento is a nightmare to work with</a> (if that looks like a fun time go for it). In my experience Django/Satchmo are much more flexible and easier to customize, as well as easier to maintain, plus you can take advantage of <a href="http://djangopackages.com/" rel="nofollow">Django's rich ecosystem of packages</a>. And seriously Python > PHP.

In the long run I think you'll be much better off with Django/Satchmo. At some point in the distant future (because no project is ever truly finished, nor as simple as your initial requirements might imply) your client will come back and say "Oh, well...we really wanted X to happen when user Y does Z". And at that point you'll either say "Sure no problem, your site is built on Django so that's a piece of cake!" or go into convulsions because you'll think of all the work that will entail with Magento.

blocks|key|3051593|text|这已经超过了最初海报的时间限制，但是如果您使用Django，Cartridge/Mezzanine是一个很好的电子商务设置。它有一个Ubuntu部署脚本，Stripe集成，并且是可定制的。夹层|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3051594|http://mezzanine.jupo.org/|offset|length|3051595|您可以将夹层添加到现有的Django项目中。http://mezzanine.jupo.org/docs/frequently-asked-questions.html#how-can-i-add-mezzanine-to-an-existing-django-project|3051596|不错的夹层教程：http://www.rosslaird.com/blog/first-steps-with-mezzanine/|3051597|entityMap|0|LINK|mutability|MUTABLE|url|1|http://mezzanine.jupo.org/docs/frequently-asked-questions.html#how-can-i-add-mezzanine-to-an-existing-django-project|2|http://www.rosslaird.com/blog/first-steps-with-mezzanine/^0|0|0|Q|0|0|M|38|1|0|8|1L|2|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]|Q|$5|M|N|O|A|$P|R]]|S|$5|M|N|O|A|$P|T]]]]

This is past the time constrains of the original poster, but if you're using Django, Cartridge/Mezzanine is a nice setup for e-commerce. It has an Ubuntu deploy script, Stripe integration, and is customizable. Mezzanine is 

<a href="http://mezzanine.jupo.org/" rel="nofollow">http://mezzanine.jupo.org/</a>

You can add Mezzanine to an existing Django project.
<a href="http://mezzanine.jupo.org/docs/frequently-asked-questions.html#how-can-i-add-mezzanine-to-an-existing-django-project" rel="nofollow">http://mezzanine.jupo.org/docs/frequently-asked-questions.html#how-can-i-add-mezzanine-to-an-existing-django-project</a>

Nice Mezzanine tutorial:
<a href="http://www.rosslaird.com/blog/first-steps-with-mezzanine/" rel="nofollow">http://www.rosslaird.com/blog/first-steps-with-mezzanine/</a>

I need to develop a new site with the e-commerce part. I'm here to get some hints from you on which road I should go on.

The site will have a static part which include some static pages and the e-commerce part for sell the products. I'm a Django and PHP developer but this is the first time I need to develop an e-commerce.

I see there's some solutions like Satchmo for Django and Magento for PHP.
There's also some services like Shopify that provide a pre cooked solution.

These are my requirements:

<ul>
<li>I'll need to give to my site a custom layout/style, all written by me</li>
<li>I'll need a nice admin interface for view the incoming orders, the average orders for day and other nice stuff (I see Magento have a very nice panel for this)</li>
<li>I'll need a feature that reports me the products that are outgoing out of stock</li>
<li>Maybe I'll need to implement a custom payment method</li>
<li>Maybe I'll need to implement a custom shipping courier</li>
</ul>

Of course I prefer Django instead PHP. Anyone can give me an hint? I've never used anyone of this framework/products.

Thank you.

-- EDIT

Deadline is 3 months. Budget ~7500 $. I've three months for finish it.

E-commerce from scratch or not

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要开发一个新的网站与电子商务部分。我来这里是想从你那里得到一些提示，告诉你我该走哪条路。该网站将有一个静态部分，其中包括一些静态页面和电子商务部分的销售产品。我是Django和PHP开发人员，但这是我第一次需要开发电子商务。我看到了一些解决方案，比如Django的Satchmo和PHP的Magento。还有一些服务...

问从无到有的电子商务
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从无到有的电子商务EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从无到有的电子商务
EN