Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/k2.php on line 14
Strict Standards: Non-static method K2HelperPermissions::setPermissions() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/k2.php on line 27
Strict Standards: Non-static method K2HelperUtilities::getParams() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 18
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 284
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 18
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 19
Strict Standards: Non-static method K2HelperPermissions::checkPermissions() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/k2.php on line 28
Strict Standards: Declaration of K2ControllerItemlist::display() should be compatible with that of JController::display() in /home/mgz/t.meta98.ru/docs/components/com_k2/controllers/itemlist.php on line 16
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/controllers/itemlist.php on line 19
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/controllers/itemlist.php on line 21
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/controllers/itemlist.php on line 23
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/controllers/itemlist.php on line 25
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 19
Strict Standards: Non-static method K2HelperUtilities::getParams() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 20
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 284
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 20
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 21
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 25
Strict Standards: Non-static method K2HelperPermissions::canAddItem() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 28
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 184
Strict Standards: Non-static method K2Permissions::getInstance() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 185
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/permissions.php on line 192
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 162
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 706
Strict Standards: Non-static method K2HelperUtilities::getAvatar() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 173
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 20
Strict Standards: Non-static method K2HelperUtilities::getParams() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 21
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 284
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 21
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 62
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/item.php on line 1451
Strict Standards: Creating default object from empty value in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 176
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 178
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 185
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 21
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 23
Strict Standards: Non-static method K2HelperUtilities::getParams() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 24
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 284
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 24
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 31
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 66
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 323
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 325
Strict Standards: Non-static method K2HelperUtilities::getParams() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 326
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/helpers/utilities.php on line 284
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 326
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 332
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/models/itemlist.php on line 355
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 303
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 304
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 305
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 353
Strict Standards: Non-static method JSite::getMenu() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 354
Strict Standards: Non-static method JApplication::getMenu() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/includes/application.php on line 539
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 354
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 422
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 448
Strict Standards: Non-static method JSite::getMenu() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 449
Strict Standards: Non-static method JApplication::getMenu() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/includes/application.php on line 539
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/views/itemlist/view.html.php on line 449
Strict Standards: Non-static method JSite::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Non-static method JApplication::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/includes/application.php on line 539
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 19
Strict Standards: Non-static method JSite::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Non-static method JApplication::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/includes/application.php on line 539
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 19
Strict Standards: Non-static method JSite::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Non-static method JApplication::getMenu() should not be called statically in /home/mgz/t.meta98.ru/docs/includes/application.php on line 539
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 17
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/components/com_k2/router.php on line 19
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/templates/jbintrepid/html/com_k2/templates/user.php on line 14
Strict Standards: Non-static method Zengrid::countModules() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/templates/jbintrepid/html/com_k2/templates/user.php on line 47
Strict Standards: Only variables should be assigned by reference in /home/mgz/t.meta98.ru/docs/plugins/system/zengridframework/zengridframework/classes/j17/zengrid.php on line 225
Strict Standards: Accessing static property JDocumentHTML::$_buffer as non static in /home/mgz/t.meta98.ru/docs/plugins/system/zengridframework/zengridframework/classes/j17/zengrid.php on line 232
Strict Standards: Non-static method Zengrid::getModules() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/plugins/system/zengridframework/zengridframework/classes/j17/zengrid.php on line 232
Strict Standards: Non-static method Zengrid::_load() should not be called statically, assuming $this from incompatible context in /home/mgz/t.meta98.ru/docs/plugins/system/zengridframework/zengridframework/classes/j17/zengrid.php on line 254

The RFP Process Made Simple
Step one within the RFP process is to determine the companies you wish to consider as potential bidders in your distribution business. You could have, essentially, options: specialist firms that provide distribution services to book publishers, and book publishers who handle distribution for other publishers.
Each of those options has its pluses and minuses. Consider both—the broader you cast your net, the higher your options, as well as your understanding of the range of companies available.
Regardless of the players you consider, your RFP should be despatched to a minimal of 4 bidders, and you should enable ample time (four months, minimum) for the whole process from RFP creation to last vendor selection.
Protect Your Information
Earlier than you exchange any info, all prospective bidders should be required to sign a non-disclosure agreement (NDA). The NDA shouldn't only embrace prohibitions against divulging confidential financial and operational info provided by either party, but should contain a clause clearly prohibiting the discussion of the RFP with unauthorized parties within the publisher’s organization. Moving to a third-party distribution enterprise model is a significant step, and till the choice is finalized and a transition plan confirmed, the small print of the effort ought to be shared only on a necessity-to-know basis. Beyond the potential nervousness and disruption to what you are promoting, your negotiating leverage is diminished if your effort is affected by data leaks.
Part One: Your Wants and Expectations
An RFP should have two major sections. Part 1 should include information about your existing operations and your expectations for your business over the three to five years following the transition to the third-party provider.
The latter is particularly essential—especially in case you see your organization embracing the operational opportunities offered by print-on-demand (POD) and quick-run digital printing. As POD pricing continues to decline to near-commodity levels, printing technology improves and stock becomes virtual, the calls for on distribution facilities will undergo dramatic change—all of which should translate to reduced operating prices for publishers.
Part 1 additionally should include, at minimal, quantitative particulars for your online business’ last full, fiscal yr, together with:
Number of active prospects
Number of invoices and credit memos issued annually
Calendarized gross sales and returns—in each dollars and units
Transaction particulars, including number of units per invoice and number of lines per invoice
Number of titles in active backlist
Number of new titles printed yearly
Examination copy volume
Average number of books in storage
Specialised service requirements, together with kitting, international shipments, sticker application, re-jacketing, etc.
Writer service expectations, including time-in-process requirements for major processes comparable to revenue and complimentary-copy order achievement, returns processing, check-in and availability of incoming inventory, etc.
Be Accurate and In-depth
The quality and quantity of the information you provide may have a direct bearing on the accuracy of the bid and the quality of the working relationship between you and your distribution partner. It's a good idea to include a multiyear view of the knowledge listed above that illustrates each historic trends and prospects for the future.
Part Two: Ask the Right Questions
Part 2 of the RFP provides the prospective distribution partners with detailed questions concerning their organizations, the providers you'd like them to provide and, of course, the
associated costs.
The RFP ought to, at minimum, request the following:
• Distributor background, including history, ownership, organization chart, client list and financial statements.
• Operational descriptions. Request a list of critical warehouse, achievement and repair processes, and written descriptions together with workstream diagrams. The operations should embody order intake, pick, pack and ship, customer service, invoicing, credit and collections, and processing of incoming shipments.
• Service-stage standards. Request that the distributor provide details of service-level standards (e.g., time in process) for critical business operations.
• Stock administration, together with physical inventory processes, shrink-
management procedures, back-order reporting and management, and audit controls.
• Digital services. Several major distributors have established strategic alliances with POD specialists, digital asset management service providers and e-book distributors to offer a broader range of services. These companies supply the smaller publisher a remarkable opportunity and must be absolutely explored as part of the RFP process.
• Computer systems, including a complete description of the hardware and enterprise software in place, plans for any upgrades or replacement of the enterprise systems, EDI/ONIX capabilities, shopper information access and reporting capabilities.
• Contingency plans, together with
disaster-recovery plans for the facility and business systems, and a readiness plan in the event of a pandemic flu outbreak. A stunning number of publishers have asked their suppliers to provide their business continuity plans for managing by way of a flu epidemic.
• Customer references. While references provided by the distributor will only be from glad prospects, they are nonetheless valuable and should be completely researched.
• Charge structure. Distributors typically will quote providers on a transaction foundation or as a share of net sales. The publisher ought to specify the desirered pricing technique, however for ease of comparing prospective prices with historical spending, the percentage of net sales technique is recommended. In addition to the base costs, the distributor ought to be asked to provide a detailed list of costs that are not included in the base charge, equivalent to excess returns charges, extra inventory, customized reporting fees, etc.
• Transition costs. The move from your current distributor to your new provider is not going to be without costs. The distributor should be asked to provide an estimate of the transition bills that will probably be billed to you—if any—including inventory switch, data upload and another bills for which the distributor will expect to be reimbursed.
• Pattern contract. It is best to have your authorized advisor assessment the distributor’s pattern contract.
A Service Indicator
A carefully crafted RFP is essential to successfully evaluating the potential value of third-party distribution. The time you invest in it might be time well spent.
If you have any queries relating to in which and how to use rfp management SaaS, you can get in touch with us at our own web-page.