Show HN: CropUp, Sell your _______ on _______
cropup.com
cropup.com
For example, I got: YouTube, Tumblr, YouTube, YouTube, Twitter
Yep, we noticed that as well, will fix it. Excellent observation, thank you.
Thanks for the feedback. Really appreciate it :D - It's now sequential! (yay~) We also modified it slightly to (hopefully) make the idea "you can sell _anything_ on _anything_" clearer. Any thoughts?
BIG QUESTION: why PayPal for disbursing funds? With Stripe and BalancedPayments as options, I'm not sure why you'd use PayPal (other than possibly international reach).
Good question. PayPal was the easiest to use, for now, and works well. We'll likely add additional payout options, but no concrete plans or timing just yet.
Nice job with Cropup!
We see shopping cart providers as our competition and they usually charge setup and/or monthly fees, which we do not. Given the value and functionalities our product provides we feel our pricing is fair, but we're open to structuring it differently in the future depending on market feedback, like volume or product price based, or we introduce a premium account with a monthly fee but lower per transaction fees.
Fair point. We're open to exploring other pricing structures based on the market feedback we'll get. In general, goal is to rather be the Apple of eCommerce than the Dell. (Well, that sounds cheesy and not in a good way :) Sorry.) We don't want to be the cheapest service but the one that provides our sellers with the most value.
It seems that since the orders will be coming through CropUp, why not hold the hand of the merchant just a few steps further? Intake orders, print shipping labels, provide shipping materials to merchants, One-Stop-Shop concept.
Excellent thinking! This is one of the ideas on our list, no concrete plans or timing yet though. It should just be real simple to sell the products you make so that you can spend more time on the things you actually care about like making some cool products.
Thanks! That's a great point and we're in the process of creating a few more product screenshots and possibly a video demo to cycle in that header area. In the mean time feel free to take a look at it here: http://crop.to/fW
Outsch. We're fixing that as we speak. Our apologies.
So then you only support physical products for now, or also digital ones (no shipping, etc)?
Thanks for the feedback and we're working on a test product feature for sellers.
Yes, we only support physical products for now. Digital goods will be coming soon.
Are there specific use cases that CropUp provides more value? Eg. on physical products? Photography? Digital downloads?
I ask because I see more and more similar products cropping up (pardon the pun) which want to help anyone sell anything online, but can't help but think that focusing on a specific vertical may result in the platform providing more value to the sellers.
For now we're focused on physical products, which come with a couple of challenges sellers of digital products usually don't have to worry about, like taxes, fulfillment, returns/refunds, etc. Our goal is to provide a product that equips sellers with everything needed for selling online and to make it real simple, so that they can focus on making their products and don't have to worry about selling them.
Maybe you should add more text to that page.
Interesting. Would you be able to provide me with a link to where I can read more about this, please? Would be very helpful. Thank you.
Directives are implemented differently in different EU countries and the countries also have the option to impose stricter rules.
In Denmark, consumers have the right to return digital goods such as e-books etc within 2 weeks (provided they haven't started using the product). I have no idea how it is in other EU countries but I would not be surprised if several other countries protect consumers that way.
Most Danish sellers of digital products state in their terms that the right of cancellation only applies until the file (e.g. an e-book) has been downloaded. I am not sure that would hold up in court.
As for VAT, in the European Union this is regulated by an EU directive on the common system of VAT: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CONSLE... Article 58 and Annex II deal with electronic services (and goods). Also look at the temporary rules in article 357 and forward.
As for taxes, every country has it's own rules and you will probably also have to consult double taxation treaties.
These issues are very complicated. If your website sells in different countries you should probably consult with accountants from each country.
Thank you. This doesn't look like a lot of fun to read... Will suffer through this. Again, thank you very much. Very helpful, very appreciated.
I shall and I will. Thank you very much.
You're right. We need to -- and will -- figure something out to better convey the buyers' end to end experience to people interested in using our service to sell their products.
I'm not sure if you have (or intend) to support people with a lot of products, but I'd be interested to see how it works if you have 50 products vs. 500 vs. 5000. It would be nice to get group reporting (like every color of a T-shirt combined, all my mugs, etc. Ideally with tags instead of categories so you can cross-report).
We have some interesting ideas for what we can do with pricing in the future, like based on volume or product price or maybe we introduce a premium account that comes with a monthly fee, but lower fees per transaction. Still thinking about these.
For now we think 10% is a fair price given the value and the functionalities our product provides, e.g. calculating taxes based on the seller's nexus states and the buyer's shipping address. Also, the seller is only charged a fee in case of a successful order, but not e.g. in case of a refund, which is different from other services like e.g. PayPal. (And different means better here, we think.)
You're right, we need to make pricing more visible.
We can't reproduce that issue. Did you try to clear your cache?
If you're still having that issue, can you send me an email: robert@cropup.com
Thanks! I completely agree with you on getting a video for the homepage, and we're actually in the process of creating one (they just take some time), as well getting a product demo link up.
http://cropup.com/help/merchant
What about international buyers?
Yep, no problem. You can accept payments from international customers.
Hmm. I'm not following, can you please explain? It's not US only and that's what the FAQ says / is supposed to say.
But.. if you give money to sellers with PayPal, you're paying PayPal fee?
Correct, great observation. PayPal Masspay charges the payment sender a fee, but it's free for the recipient. So these payouts are free for our merchants.
Would you imagine something like a pub/sub system or something that you would ping?
For digital goods, we'd handle the fulfillment for you. Goal is to make it dead simple and to provide everything you'd need, so you don't have to use any other services or do any coding.
Still, a server to server notification would be a good thing to have, no concrete plans or timing yet though.
Thanks for your feedback.
It's for anyone who wants to sell a product on a social network like Facebook, Twitter, etc., whether you have an online store already or not. It's not great to share a link to your online store on social networks because then your customers have to go through the entire checkout flow incl. putting the item into the shopping cart, going to the shopping cart, clicking on checkout, creating an account or not, ... even though all they want to do is buy one specific item quickly and easily. With CropUp you can sell individual products via a very streamlined checkout flow, that works great regardless of the social network or the customer's device (mobile, tablet, desktop).
I'm surprised how well AngularJS has worked for us.
Currently, we're using it for the shopping checkout page and also for the merchant dashboard. The dashboard is all driven by AngularJS (using $resource/$http api calls). The checkout page is more like Twitter, in that we preload data in the DOM when it's rendered, but there are API calls via AngularJS to create the order, check quantity, etc. These pages are actually served directly from our CDN.
As far as how it's worked for us. We've actually rewritten our dashboard and checkout page twice, and it look some getting used to on how to structure our controllers. Getting used to writing directives instead of using jQuery and doing DOM manipulation in our controllers also takes some discipline, because it's just way simpler to drop some selectors and event bindings/triggers in your controller.
The way AngularJS encourages you to keep any dom manipulation out of the controller and to think about reusable directives has really helped for readability and maintainability of the code base. We're consistently surprised how quickly we can implement features because of AngularJS. We've actually said, "Wow, that was easier than I was expecting" quite a few times.
However, there are some hurdles. $http doesn't support file uploads, the stable release doesn't support custom http headers with $resource, only one ngView, etc. That said, I still would not hesitate to recommend AngularJS.
Totally agree with Jack on this, I enjoy working with AngularJS. I think the learning curve could be made less steep with better docs. It would be great if they were moved to GitHub to make contributing easier.
[1] https://groups.google.com/forum/?fromgroups=#!topic/angular/...
You really really really really want to keep those kind of things in directives.
Anyway, I read about it sometime ago on a github issue it is 'planned'.
In the first iteration, we thought multiple ngViews would have been useful, but it didn't prevent us from achieving the design we wanted. You can use ngInclude to accomplish a similar effect, if you don't need the routing.
AngularUI seems to have a solution for nested views/routing here (https://github.com/angular-ui/ui-router). Although, I would think about your routes and the pieces of your web application and rethink whether you really need ngView. Using ngIncludes for pieces you want to reuse might make more sense.
edit: for clarity
I'm not familiar with them, but I'll check them out now. Have you used them? Do you like them?
Based on the other comments here you can tell we use neither Stripe nor Balanced :) One of the other big guys... Please email me if you'd like to discuss details: paul@cropup.com