Below is an explanation of what is meant by “scope”, why it’s important, and how such requests are typically handled.

Why is a scope important?

We often see customers experimenting with integrations on their own, only to run into technical limitations or incorrect assumptions. Without a clear framework, it becomes difficult for us to offer targeted assistance.

Providing a scope helps us to:

• understand your goals and context
• assess whether your request is technically feasible
• offer advice on the best tools and approach
• avoid unnecessary delays, miscommunication or frustration

What do we mean by a scope?

A solid scope outlines what you want to achieve and which processes, tools, and data flows are involved. At a minimum, we need the following information:

• 1. Project goal
  What are you trying to accomplish? For example: "We want to send webshop orders directly to MultiPress."
• 2. Systems or tools involved
  Which platforms or software are you integrating with MultiPress? Think of webshops, ERP, CRM, planning tools, email systems, cloud storage, etc.
• 3. Data flows
  What data do you want to exchange or automate? This could include orders, customer info, planning, stock levels, files, approval steps, etc.
• 4. Current workflow
  How are you currently working, and where are the bottlenecks? This helps us better understand your situation.
• 5. Who will develop the integration?
  Will your own developer build it, an external partner, or do you expect support from us?
• 6. Timeline and priorities (optional)
  Do you have deadlines or phases? Are there parts of the project that are more urgent than others?

What do we do with your scope?

Based on the scope you provide, we can prepare a quote for a functional analysis. This is a paid service and follows these steps:

1. You submit your scope in writing
   This can be sent by email or as a document. A written scope is always required as a starting point.
2. Intake meeting (if needed)
   If anything is unclear, we’ll schedule a short intake call with one of our Application Specialists to fine-tune your scope.
3. Quote for a functional analysis
   Based on the scope (and possibly the intake), we’ll send you a quote. Work only begins after your formal approval.
4. Functional analysis by our solution architect
   You’ll receive a detailed document describing:
   • what’s technically possible
   • which tools or API methods can be used
   • which steps your developer should follow
   • any risks, limitations or important considerations
5. Development & support
   Your developer can get started with the analysis as a guide. If needed, we can offer additional support — again based on a quote or predefined support model.

What if you decide not to follow this process?

If you choose not to proceed with a scope and analysis right away, that’s completely fine. However, please be aware:

• If you contact us later with questions or issues related to a self-built integration, we may not be able to offer direct support without first going through the same scoped analysis process.
• This ensures we fully understand the context and can give meaningful, reliable advice.
• In these cases, we will again propose a quote for a functional analysis before offering further assistance.

This approach helps maintain quality, avoid misunderstandings, and ensure long-term success.

In summary

A well-defined scope is essential for a smooth and successful integration. It ensures we can guide you efficiently and that your investment pays off.

Not sure how to get started? Just reach out — we’re happy to help.