Question 1

Does my data leave my network when using Qwen?

Accepted Answer

No. Qwen runs on hardware you control, so the prompts and the operational data stay inside your network. Use it where sending shipment or customer data to a third party is not permitted.

Question 2

What hardware do I need to run Qwen?

Accepted Answer

It depends on the parameter size you choose. Ollama serves the same model family at several sizes, so a smaller variant runs on modest hardware while a larger one wants a dedicated GPU. Start small, measure answer quality on your own questions, and move up only if it falls short.

Question 3

Can I use Qwen alongside a hosted provider?

Accepted Answer

Yes, and that is the common setup. Routine questions run locally on Qwen while heavier analysis routes to a frontier provider, and routing falls back to the local model automatically when a hosted provider is rate-limited.

Question 4

Why Qwen?

Accepted Answer

Language coverage. Qwen handles vendor correspondence, customs descriptions, and carrier documents in Chinese, Japanese, Korean, and the European languages better than most open-weight models, and its tool calling holds up in agent runs.

Question 5

Which other models can I run alongside Qwen?

Accepted Answer

Any of them, and more than one at a time. CommerceShip runs ChatGPT, Claude, Gemini, Mistral, and Muse as frontier models, and DeepSeek, Gemma, GLM, Kimi, Llama, MiniMax, Nemotron, and Qwen as open-weight models, served through Ollama Cloud or on your own hardware. Route routine work to one model and heavier analysis to another, and if a provider is rate-limited or down, the run moves to a fallback and completes.

Question 6

What access does CommerceShip need to Qwen?

Accepted Answer

The connection uses scoped credentials limited to the record types the integration works with, and you choose which fields are included. Credentials are encrypted at rest and stored separately from your operational data. Revoke the connection from either side at any time and the access ends with it.

Question 7

How is my data protected?

Accepted Answer

TLS in transit and AES-256 at rest, with tenant isolation enforced by row-level security in the database. Role-based permissions control who on your team can see cost data or change carrier settings, and automated actions are written to an audit log. CommerceShip is pursuing SOC 2 Type II certification. The security page carries the full detail.

Run supply chain AI locally with Qwen

Qwen Integration Capabilities

How the Qwen integration works

Connect your Ollama

Assign Qwen to the work

Ask and act

Qwen Integration FAQs

Keep Qwen inside your network

Other Models