Our workflow does not fit any existing software.
When is a dedicated application worthwhile? How can a first scope be limited, what influences the costs and how does a project start without a finished specification?
To the answersQuestions and answers
What would you like to clarify before the next step?
Perhaps it is about costs, an existing application, contradictory data or whether you need new software at all. Choose the situation that comes closest to your concern.
Search for a question or keyword
Search 144 questions directly.
For example: costs, source code, ERP, interface, offline, hosting or data export.
144 questions in 28 topics.
What is your situation?
Our existing software is important – but changes are getting harder and harder.
What is possible when documentation, tests or knowledge are missing? How do we check whether an application can be taken over, stabilised and developed further?
To the answersWe transfer the same data between several systems.
Which system should lead customers, products, prices or orders? How do errors become visible, and how can retries work without duplicates?
To the answersWe have an idea for an app – but do not yet know what is technically needed.
Is a mobile web application enough, or do you need an app? What role do the back end, offline use, publication and ongoing maintenance play?
To the answersOur shop sells – but there is still a lot of manual work behind it.
Where should product data, prices and stock be maintained? How do orders reach the ERP reliably, and when is a standard system no longer enough?
To the answersExcel and email are no longer enough – but a complete new ERP would be too much.
Can Workspace start with a single area? Which systems can stay, and how do shared cases, responsibilities and statuses come about?
To the answersIs there already an app for our specific task?
Which task does each schukai app solve? On which platforms is it available, does it need an account or a cloud, and where can you find the price and support?
To the answersWe would like to know what we are getting into with a software project.
What do you need for the first meeting? How are scope, changes and acceptance handled? Who looks after hosting, backups, updates and support later?
To the answersAll answers
All questions by topic.
The technical terms help you find your way. Use the search field if you already have a specific keyword in mind.
About schukai
Custom software development
- How can we tell whether we really need custom software?
- Does custom mean everything is programmed from scratch?
- Can we start a project even though we do not have a specification yet?
- Why can quotes for seemingly the same software vary so much?
- How do we avoid becoming dependent on a single provider after development?
Business applications and web software
- When are Excel, email and shared folders no longer enough?
- What is a business application at schukai?
- Can a business application complement our ERP without keeping data twice?
- Which process should we start with?
- How are roles, permissions and approvals mapped?
- Can existing Excel lists and legacy data be taken over?
App development
- Do we really need a native app, or is a web application enough?
- Does schukai develop for Android and iOS?
- Are back end, sign-in and synchronisation part of app development?
- Can an app work without an internet connection?
- Who owns store accounts, signing keys and source code?
- What costs arise after the first release?
- Does an internal company app have to appear publicly in the app store?
Taking over existing software
- Can schukai take over an application built by another developer?
- What happens if there is no documentation?
- Does schukai need the complete source code?
- Isn’t a complete rebuild cleaner than continuing the old software?
- How do we keep operations running during the takeover?
- Why is a paid technical check often needed before a takeover?
Back ends and interfaces
- What is the difference between an API, an interface and an integration?
- Is it enough if both systems have an API?
- Which system should be the leading one in an integration?
- How do you prevent duplicate orders or lost transfers?
- Where do staff see that a transfer has failed?
- Does an interface always have to work in real time?
- How are interfaces secured and prepared for changes?
Shop and customer portal
Online shop
- Can schukai develop our existing shop further?
- What does a shop migration involve besides products and design?
- Should the ERP lead products, prices and stock in the shop?
- How can overselling across several sales channels be avoided?
- Which costs of an online shop are often overlooked?
- Can special ordering rules be added to a standard shop?
B2B customer portal
- Which functions should a B2B customer portal offer first?
- How are customer-specific prices and product ranges displayed?
- Why shouldn’t a customer portal simply give direct access to the ERP?
- Does a B2B portal have to allow orders?
- What should we do if our internal data and statuses are not yet clear?
- How do you introduce a B2B portal without switching all customers over at once?
Product data
- Which system should be the leading source for product data?
- Do we need a PIM, or is the ERP or Workspace enough?
- How are variants, technical attributes, images and documents kept together?
- How do we know whether a product is complete and ready to publish?
- How is existing product data cleaned up and migrated?
- Can AI generate product texts and attributes automatically?
Shopcloud by schukai
Workspace overview
- What is schukai Workspace?
- Is Workspace a complete replacement for ERP, CRM or document management?
- Can we start with a single area?
- How does Workspace differ from a custom-built business application?
- How much configuration and customisation is possible?
- How are prices and licences for Workspace determined?
Workspace: customers and orders
- Which customer data and cases can be brought together in Workspace?
- Does the customers and orders area replace our CRM or ERP?
- How do status, responsibility and the next step stay clear?
- Can quotes and orders be linked to documents and emails?
- How are multiple companies, locations and contact persons mapped?
Workspace: inbox and cases
Workspace: products and commerce
Workspace: service and field service
- What information can a service technician receive on site?
- Does field service work even with poor network coverage?
- Can times, materials, photos and signatures be documented?
- Can job data be passed on to ERP, billing or the warehouse?
- How do you prevent the mobile interface from adding to the technician’s workload?
Workspace: warehouse and shipping
- What is the difference between stock and available quantity?
- Does Workspace replace a complete warehouse management system?
- Can barcodes, scanners and mobile devices be used?
- What happens if the network is down or synchronisation is delayed in the warehouse?
- How are shortages, damage, partial deliveries and other exceptions documented?
Workspace: integrations
Apps overview
PickQueue
raus
Workspace App
WithinCells
Proofara Receive
OshiYa
Approach
- What should we prepare for an initial consultation?
- When does a paid process or technical check make sense?
- Does schukai work at a fixed price or on a time and materials basis?
- Who on the customer side needs to work on the project?
- What does MVP or first production scope mean at schukai?
- How do acceptance, testing and change requests work?
Technology and operations
- Can schukai run software in the cloud, separately or on-premises?
- Where is data stored, and do we need a data processing agreement?
- How do backups work and how often is a recovery tested?
- How does schukai protect applications and interfaces?
- What does support cover, and what is further development?
- How are errors noticed before a customer or employee reports them?
- Can we export all our data when the contract ends?
- Who owns the source code, repository, domains, accounts and technical keys?
Partners
Your question is not listed?
Ask us directly.
Tell us briefly what it is about. We reply within one working day.