Product development is everything related to your product catalog published on your Print Stores. It can be in form of category landing pages and/or product templates accessed with the Print Editor.
Carefully planning a web-to-print e-commerce website is essential to its success, and your product catalog decisions are at the heart of that process. We ask the following product and catalog questions when planning a new eCommerce website with our customers.
Web-to-print sites go beyond standard shopping cart items and support many print product types offered in different ways. When defining your product catalog in PrintNow, be aware of all the available product types and methods you want users to interact with your product pages.
Once you understand the different product types available for your products, you can determine how many products you will be selling of each type. It will impact how long it will take to develop the store (more products = more content to create and load into the Print Store).
We also need to know how to organize your product catalog. The navigation and search in your online store will be how your customers find your products. Planning how your products will appear will impact your Print Store development and how well it converts visitors to customers.
That’s where pricing with order options comes in. Pricing may include available Quantities, Printed Sides, Sizes, Turnarounds, and order options like Paper Stock, Folding, or Proof options. So, we’ll ask you what option groups your products have in the planning stage and what option items are under each group. You’ll be able to edit your actual prices by exporting and importing after the basic setup is complete.
The creation and loading of product information can be time-consuming. Most people underestimate how long it will take. It is the leading cause of delays in launching new eCommerce websites. Most eCommerce developers (including us) will assume that you will supply and load all product information yourself unless you specifically ask us to do it for you. You’ll usually need to provide the following information as a bare minimum:
Categories
Products
Most eCommerce websites follow a fairly generic approach to presenting product pages. If you need anything different, we need to know about it.
The generic approach will usually include the following:
In addition, you may have different types of products that need to be displayed differently. We need to know this too. For example, some pages may default to a product browser with many versions and filters, and others will have one product landing page with specific action buttons.
Related Product displays are great for upselling, but their implementation can be complex or straightforward. We need to know whether you want to include related product displays on product pages. Including them will involve some configuration of the eCommerce platform during development. The visual design will also need to take account of these on the product page displays. Some options for Product displays include:
Related Product displays are great for upselling, but their implementation can be complex or straightforward. We need to know whether you want to include related product displays on product pages. Including them will involve some configuration of the eCommerce platform during development. The visual design will also need to take account of these on the product page displays. Some options for Product displays include:
These are the main questions we ask customers about their products and product catalog when scoping and planning a new eCommerce development project. There is a lot to consider here – but the scoping process will go faster, and you will be better informed about what you will get at the end of reviewing it.
Price: TBD
Setting: Remote
Duration: TBD
Product Development
Hourly rates range from $125 to $250 per hour, depending on the experience level of the developer/consultant and if it’s standard front-end development or requires back-end development that affects the core PrintNow code base.
The short answer is we offer both, but generally, customers are more comfortable with a per-project flat rate. Overall, the pricing structure you choose depends greatly on many variables and comes down to what makes the most sense for you.
Charging per hour
Charging an hourly rate is a better option in some scenarios. If the scope of work isn’t clear from the outset, we may recommend this approach. Or we may offer a service to properly define project details to help it move to a per-project flat-rate option. Per-hour pricing also works well for maintenance updates or long-term ongoing projects.
Charging a per-project flat rate
Charging a flat rate makes the most sense when the client brief is clear and structured, and we can predict how much work the project will entail. Some clients are more hesitant to agree to a flat rate. Presenting one flat rate before any work is done can make some clients nervous or cause sticker shock, prompting them to go elsewhere.
Scroll down to the bottom of this page and submit the online form after clicking on the “Request more information” button. A technical consultant will contact you to schedule a meeting with a broad understanding of all development services to investigate further.
Want to learn more? We can help find the service that’s right for you.