What a model upload means in getPrintiv

getPrintiv is a quote-to-checkout storefront for 3D print shops. The platform brings catalog sales, custom quote intake, and customer handoff into one place for shops that sell catalog items and custom work online. A 3D print model upload is one of the quote request starting points inside that workflow. The same request flow can also start from a reference URL, an image upload, or a scan request, and each quote request requires either an email contact or a phone contact.

Accepted model upload formats are .3mf, .step, .stp, .stl, .obj, and .zip, with a file size limit of 200 MB. That accepted-format list is the file boundary for the model-upload path: .3mf, .step, .stp, .stl, .obj, and .zip are accepted inputs, and the maximum upload size is 200 MB. getPrintiv treats those file types as accepted inputs for quote intake, then keeps the quote request inside the shop workflow instead of presenting the upload as an instant production decision.

Review comes before approval

The model upload does not mean automatic printability approval. A getPrintiv shop reviews quote submissions and confirms printability. That is an important boundary for customers and shop operators: the upload starts the request, while the shop still decides whether the work can move forward. getPrintiv admins can approve or reject quote requests, and an approved quote requires a priced item. The public catalog can then include approved quote work or admin-published parts that have public visibility.

This separation keeps the shop review step in the workflow. The customer can begin from a model file, reference URL, image, or scan request. The shop can review the submission, decide whether it is printable, and approve or reject the quote request. When a quote is approved, the quote has a priced item before it moves into the order path. Those facts are the practical center of the model upload workflow: upload begins the intake, review controls approval, and the shop remains responsible for the production decision.

Where checkout and order status fit

getPrintiv shops have a hosted storefront, quote operations, customer-ready order status, checkout, and admin access. Orders can check out as guest orders or signed-in orders. Checkout requires an email or mobile phone contact, opens payment in Stripe Checkout, and keeps order details in the app. That means the customer handoff is not only the first upload screen. It continues through quote review, approved work, checkout, and order status details that the customer can understand after the order exists.

The order fulfillment statuses in getPrintiv are new, queued, printing, quality_check, ready, out_for_delivery, delivered, and archived. Those labels describe the order-status vocabulary that appears after a request has become an order. For a model upload guide, the point is not that every uploaded file becomes an order. The point is that the product has a path from quote intake to checkout and then into status tracking when the shop approves the work and the customer completes checkout.

Shop setup context

A getPrintiv shop is created with Google sign-in, a shop name, and a shop URL slug. A shop uses a hosted subdomain at the chosen slug on getprintiv.com. That setup context is useful when thinking about model uploads because a getPrintiv tenant shop uses a hosted subdomain at the chosen slug on getprintiv.com. The customer is interacting with a shop storefront, the shop is receiving quote intake, and order details stay in the app.

In plain terms, the safe way to explain getPrintiv's 3D print model upload flow is this: accepted model files can start a quote request, contact information is required, the shop reviews the submission and confirms printability, admins can approve or reject quote requests, approved quote work can become public catalog work when made public, and approved orders can move through checkout and order statuses. That is enough to describe the upload flow without claiming instant quotes, automatic printability approval, or outcomes the product does not promise.