Do not pick a vendor on demo sites and a low number. Ask about process, permissions, APIs, acceptance and whether source code is in the handover.
Software companies differ less on whether they can write code and more on whether they can turn your documents into roles, logs and interfaces. A marketing site, a packaged ERP and a system built from your forms are three different purchases. If the pain is finding goods, waves and PDA work, evaluate WMS — do not accept an inventory screen as warehouse execution.
Lowest price before scope is frozen comes back as change orders. Headcount in the pitch is weaker than two people who can walk a real outbound. A generic admin demo proves they can open a template — not that they can handle your exception documents.
You should see a scope memo, an interface list, environments and a defect window. Custom work also needs a permission matrix and a definition of master data. MonkeyTech writes those before coding starts.
Discovery and acceptance benefit from being in the room. Coding can be remote. We are based in Foshan; Pearl River Delta visits are routine. Farther projects are remote discovery plus on-site at the milestones that need it.
Ask whether masters, approvals and interfaces can follow your rules. If the critical flow cannot change, you are buying a package, not custom software.
Ask them to design one real module out loud — permissions and failure states — instead of reading industry nouns from a slide.
Send a current form or screenshot to /en/contact/. You do not need a tender pack to start a scope.