Phiz - Pharmacy

Hi, hope you are doing fine.
We have understood your needs. Currently there are a lot of development needs, we will schedule the development as soon as possible according to the priority and urgency. I will contact you if there is any news.
Thanks

Cissy 崔敬仪 escreveu (#note-4):

Hi, hope you are doing fine.
We have understood your needs. Currently there are a lot of development needs, we will schedule the development as soon as possible according to the priority and urgency. I will contact you if there is any news.
Thanks

@Cissy 崔敬仪
Obrigado pelo retorno, os chamados aberto no projeto farmácia todos são de prioridade imediata, essas exigências são primordiais para a implantação do sistema no cliente

Hi, we are now developing more projects. This requirement has been recorded in the requirements pool and will be followed up with scheduling. I will notify you as soon as I have any news. Thanks.

Cissy 崔敬仪 escreveu (#note-13):

Hi,
We are troubleshooting this bug and the deadline has been updated in this page.
Thanks.

Olá boa tarde,

O a impressão do reembolso está funcionando perfeitamente. Agora, como faço para receber no caixa este cupom de reembolso?

Obrigado

Bom dia, registre um voucher para o mesmo preço por meio do formulário de devolução, você pode comprar o mesmo preço de mercadorias; registre o fluxo de transações relacionadas às instruções correspondentes, planejamento de demanda

11月28日会议已沟通：
记录一个通过退货单子换同等价格的代金券，可以购买同等价位商品 ；记录流水交易相关有对应的说明，需求策划

kiki zeng escreveu (#note-15):

Bom dia, registre um voucher para o mesmo preço por meio do formulário de devolução, você pode comprar o mesmo preço de mercadorias; registre o fluxo de transações relacionadas às instruções correspondentes, planejamento de demanda

11月28日会议已沟通：
记录一个通过退货单子换同等价格的代金券，可以购买同等价位商品 ；记录流水交易相关有对应的说明，需求策划

Boa tarde a todos

Tem previsão de resolução? Pois já estamos implantando as farmácias e precisamos de um prazo para dar continuidade as implantações.

@Lucas Lisboa @Cissy 崔敬仪 @henry 吴健

Obrigado

Hi, hope you are doing well
We are organizing now. The technical will start next week. If there is a deadline, I will update here immediately.
Thanks a lot.

Hi, hope you are doing well
This issue has been released already. Please test according to the Redmine content and google version guide. If there is no problems, please "resolved". If not, feel free to contact me.
Thanks a lot.

Hi, hope you are doing well

I think there is a deviation in our understanding of the logic of this feature and I have attached text to clarify and answer your concerns.

According to the requirements we discussed at the meeting, the feature is intended to be used in a business situation where the merchant doesn't want to actually give the customer a refund, but instead uses the purchase amount to be credited against the next purchase. (See google docs for details on this feature)

I'll give you an example:

Customer Nina spends $10 for the first time and asks for a refund. After negotiation with Nina, the merchant allows Nina to spend $10 off instead of a direct refund the next time he comes to the store, and when Nina enters the store again to spend $15, he presents his $10 receipt for credit. At this point, Nina only needs to pay another $5.
Merchants at this time do not need to $10 of the refund operation, only in the settlement of the “consumption credit” way, scanning the receipt's barcode for credit. After all the payments are completed, because it is not a refund operation, so the system will only record the second purchase of $5.

Based on this logic, the refunded receipt cannot be credited. The receipt that has been credited cannot be refunded either.

Now, I will answer your concerns below:

1. Because there are currently a large number of payment methods, we have used a scrolling view for aesthetics. We can design it again, but it will still take time. If it does not affect the normal operation of the merchant, this requirement may be canceled first. (We have subsequent plans to revamp the page style as a whole, and we can take this into consideration at that time.)
2. The error message is due to the fact that you made a refund first. The reason for this is explained in the text above.
3. I don't really understand the phrase "Não finaliza o recebimento do reembolso;".
4. This problem is the one shown in video "7380 (1)", right?
You can first check what method of payment this order was made. Because the system logic is to prioritize the return of the payment by the original payment method.

If there are also some doubts, feel free to contact us. And also it's possible to plan a meeting after our vacation, just leave a message to me by Phiz.

Thanks a lot.

Cissy 崔敬仪 escreveu (#note-26):

Hi, hope you are doing well

I think there is a deviation in our understanding of the logic of this feature and I have attached text to clarify and answer your concerns.

According to the requirements we discussed at the meeting, the feature is intended to be used in a business situation where the merchant doesn't want to actually give the customer a refund, but instead uses the purchase amount to be credited against the next purchase. (See google docs for details on this feature)

I'll give you an example:

Customer Nina spends $10 for the first time and asks for a refund. After negotiation with Nina, the merchant allows Nina to spend $10 off instead of a direct refund the next time he comes to the store, and when Nina enters the store again to spend $15, he presents his $10 receipt for credit. At this point, Nina only needs to pay another $5.
Merchants at this time do not need to $10 of the refund operation, only in the settlement of the “consumption credit” way, scanning the receipt's barcode for credit. After all the payments are completed, because it is not a refund operation, so the system will only record the second purchase of $5.

Based on this logic, the refunded receipt cannot be credited. The receipt that has been credited cannot be refunded either.

Now, I will answer your concerns below:

1. Because there are currently a large number of payment methods, we have used a scrolling view for aesthetics. We can design it again, but it will still take time. If it does not affect the normal operation of the merchant, this requirement may be canceled first. (We have subsequent plans to revamp the page style as a whole, and we can take this into consideration at that time.)
2. The error message is due to the fact that you made a refund first. The reason for this is explained in the text above.
3. I don't really understand the phrase "Não finaliza o recebimento do reembolso;".
4. This problem is the one shown in video "7380 (1)", right?
You can first check what method of payment this order was made. Because the system logic is to prioritize the return of the payment by the original payment method.

If there are also some doubts, feel free to contact us. And also it's possible to plan a meeting after our vacation, just leave a message to me by Phiz.

Thanks a lot.

Boa tarde a todos

Entendi a lógica, está funcionando, parabéns ao envolvidos, mas...

Temos a seguinte situação.

- Cliente comprou o produto, foi impressa a NFcE e o recibo, cliente retornou solicitando um reembolso para comprar outro produto.

- Ao escanear o recibo em "Compensação de consumo", o sistema tem que cancelar a NFcE referente a primeira compra e emitir a NFcE do produto escolhido.

Segue vídeo. https://drive.google.com/file/d/19gWEPELuzTJ-5-9nj34VzOHA_UwHLrju/view?usp=sharing

@Cissy 崔敬仪 @henry 吴健 @Lucas Lisboa

Obrigado

Hi, hope you are doing well
I'm so sorry that the payment confirmation popup was a bug. We made the change. Once you have scanned the barcode, press the keyboard "Enter" to confirm the payment directly. You can check and test it again.
However, I didn't understand clearly "- Cliente comprou o produto, foi impressa a NFcE e o recibo, cliente retornou solicitando um reembolso para comprar outro produto.". Does exist any questions here in this situation?
Regarding "- Ao escanear o recibo em "Compensação de consumo", o sistema tem que cancelar a NFcE referente a primeira compra e emitir a NFcE do produto escolhido.", Once the credit is confirmed, the system will automatically cancel the nfce for the first purchase. And also there is no change to the nfce process for the current purchase (the second purchase). You can still issue invoices as normal.
Thanks a lot.

Hi, hope you are doing well
Ok. Waiting for your meeting. Feel free to contact me.
Thanks a lot.

Hi, hope you are doing well
We explained this issue on our last meeting 26th. If there is no problem, please "Resolved" it. Feel free to contact me.
Thanks a lot.

Cissy 崔敬仪 escreveu (#note-38):

Hi, hope you are doing well
I think I get what your mean. Yes, even if the "Other payment" method is chosen, the system should not merge the records into one; instead, they should be recorded separately. We will fix this problem. If there is a deadline, I will update here inmediatly.
Thanks a lot.

Boa tarde a todos

Não tem como registrar separadamente, esta opção é inviável, isso tras transtorno ao cliente em ter que ficar excluindo produtos da venda recebendo apenas um cartão e depois lançar os outros produtos e receber com outros cartões.

A versão anterior funcionava normalmente a opção de receber mais de 2 cartões

Precisamos de uma solução urgente, preciso atualizar os clientes ativos por conta dos outros chamados que foram resolvidos.

@Cissy 崔敬仪 @Lucas Lisboa @henry 吴健

Obnrigado

Hi, hope you are doing well
I didn't understand clearly what is the meaning "isso tras transtorno ao cliente em ter que ficar excluindo produtos da venda recebendo apenas um cartão e depois lançar os outros produtos e receber com outros cartões."
I think the problem is that the use of "other payments" cannot be combined. Current situation is the system combined and recorded “Other Payments”in one method. However, should be recorded separately according to the specific method assigned by the backend.
We can clearfy the problem together and discuss a urgent solution in tomorrow meeting.
Thanks a lot.