ZhilianhaiCompany Profile: OrionStar Robotics
Company and commercial identity
OrionStar Robotics supplies commercial service robot solutions. Its official account user agreement identifies Beijing OrionStar Technology Co., Ltd. and affiliates. Buyers should establish which company or authorized regional partner signs the hardware and service contract. A software account agreement is relevant to access rights, but it is not a substitute for the equipment warranty and support terms.
Distinct service robot families
The current website separates LuckiBot delivery robots, GreetingBot reception robots, CleaniBot cleaning robots and CarryBot warehouse robots. Select the family around a defined operational task. A delivery robot's carrying functions do not establish cleaning performance, and a reception robot's interaction capabilities do not establish goods-handling capacity. Model names and regional configurations should be written into the quotation.
Restaurant delivery and collection
OrionStar's restaurant solution page describes delivery to multiple destinations, dish collection and call-button workflows. It also reports deployment at more than 70 outlets of an unnamed large restaurant chain in China as of October 2024. That is a dated supplier claim with a limited customer description; buyers should request a named, comparable reference instead of generalizing its advertised productivity figures.
Cleaning and customer interaction
The current catalogue presents CleaniBot models for commercial floor cleaning and GreetingBot models for greeting and guidance. A facility assessment should examine each task separately: floor materials, debris and water handling for cleaning; route design, language and content management for visitor interaction. Confirm which functions run locally, which use online services and what the robot can do when connectivity is unavailable.
A dated product expansion
On September 2, 2024, OrionStar announced CarryBot for micro-fulfillment applications. The release described configurable transport attachments and navigation features. This provides a dated example of portfolio expansion into internal logistics, not proof that every service model supports warehouse workloads. A launch announcement also does not establish the stock or service coverage available in a buyer's country today.
Deployment and software responsibilities
Before a trial, agree who maps the site, configures destinations, manages accounts and trains staff. Test a complete shift pattern, including charging, blocked routes, unsuccessful deliveries and manual recovery. Record how staff load or unload items, clean contact surfaces and prevent unsuitable objects from entering the workflow.
Software review should cover administrator permissions, configuration export, account handover and any recurring service charges. Ask how updates are approved and whether a change can alter routes or user-facing behavior. Define ownership of operating data and the process for transferring the system to another site.
International purchasing route
The official website provides demo and partner routes and lists global_business@orionstar.com for commercial contact. State the country, site type, task and intended fleet size. Request the proposed supplier's authorization, local-language documentation, installation scope and repair arrangements. Marketing examples from different countries are useful leads, but they do not establish universal product availability or a uniform service contract.
Questions for a service robot pilot
Which exact model and attachments fit the route and intended load?
Who configures the robot and handles daily exceptions?
What happens when connectivity, charging or a route becomes unavailable?
Which account, data, warranty and support terms apply after the trial?
Explore Service Robots, Write a Robotics Buyer Brief, or Robotics RFQ.