[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"case-detail-2702":3},{"id":4,"title":5,"client":6,"industry":7,"description":8,"serviceType":9,"projectDuration":10,"technologies":11,"result":12,"coverImage":13,"screenshots":14,"implementationDate":15,"content":16,"metrics":17,"caseType":18,"deliveryStatus":19,"verificationStatus":20,"authorizationStatus":21,"acceptanceStatus":22,"anonymizationStatus":22,"evidenceTypes":23,"evidenceSummary":24,"resultBasis":17,"sourceReferences":17,"disclosure":25,"demoUrl":17,"verifiedAt":15,"gateVersion":26,"testimonial":-1,"viewCount":27,"slug":28,"metaTitle":5,"metaDescription":8},2702,"自助洗车小程序功能方案：从找空闲车位到启动服务与异常留痕","","能源业","面向自助洗车站的功能方案，围绕车主找门店、查看空闲车位、选择服务、支付后启用服务、服务计时、订单查询与异常申报，梳理小程序、运营后台和设备接口的闭环。","MINIPROGRAM","产品方案与流程验证","微信小程序,Spring Boot,MySQL,设备接口,订单状态机","已完成能力范围、关键状态和界面交互的内部梳理。","\u002Fimages\u002Fblog\u002Fself-service-carwash-capability-prototype-20260907.webp","[\"\u002Fimages\u002Fblog\u002Fself-service-carwash-capability-prototype-20260907.webp\"]","2026-09-07","\u003Ch2>方案定位\u003C\u002Fh2>\u003Cp>本方案梳理自助洗车业务从用户进入小程序到运营端处理异常的产品与技术链路。公开页面仅展示自有演示界面和能力边界，不使用客户名称、真实门店、用户数据或设备凭证。\u003C\u002Fp>\u003Ch2>业务问题\u003C\u002Fh2>\u003Cp>自助洗车业务的关键不是单独展示一个下单页，而是让车位状态、套餐价格、支付结果、设备启用结果和异常处理记录保持一致。否则用户不知道是否可洗，门店也无法解释已付款但未启动等问题。\u003C\u002Fp>\u003Ch2>功能拆解\u003C\u002Fh2>\u003Cp>车主端以附近门店和车位状态为入口，选择服务与时长后创建订单；支付回调确认后，服务端按车位映射调用已授权的设备厂商接口，并把指令、回调和失败原因与订单关联。服务中页面展示车位、剩余时长和安全提示；订单中心可查看服务记录并提交异常。运营端维护门店、车位、套餐和优惠券，查询订单、设备日志与异常工单。\u003C\u002Fp>\u003Ch2>验证边界\u003C\u002Fh2>\u003Cp>已完成产品流程、界面设计及接口契约的内部梳理。真实设备启用需以客户已授权的设备厂商 API、测试环境、网络和现场安全规则为前提；支付、退款和会员规则须在项目启动前确认。\u003C\u002Fp>\u003Ch2>公开说明\u003C\u002Fh2>\u003Cp>页面中的门店、价格、时长、订单和会员信息均为演示数据。本条不代表客户正式交付、生产上线、设备兼容结论或经营结果。\u003C\u002Fp>",null,"INTERNAL_VALIDATION","INTERNAL","VERIFIED","SELF_OWNED","NOT_REQUIRED","BUILD,SCREENSHOT","2026-09-07 已核验自有界面图、功能清单与公开素材；公开内容仅呈现内部演示能力边界。","本条为公司自有功能方案的内部验证，不代表客户正式交付、生产上线、设备兼容结论或经营结果。页面中的门店、价格、时长和订单均为演示数据。","CASE_CREDIBILITY_V1",1,"self-service-carwash-capability-prototype",1788833123747]